At PDC I recieved a copy of VS2005 RC1 along with .NET 2.0. We discussed devoping our next application at work in .NET 2.0 since it is due out any day nowTM. Our primary third party component vendor had a booth at PDC too, so I asked me if they were .NET 2.0 ready. They said they were really close, and commited to being 100% within 30 days of actual release, any day nowTM. I figured I would see if I could port our prototype over. The result was successful. This is what I had to do:
- Built in conversion wizard when you open a VS2003 solution / project converts to VS2005.
- Required checking the files out of source control so they could be modified.
- Not very tricky, pretty straight forward.
- Removed unused references to other 3rd party assemblies.
- Set all references to the same version of the 3rd party assemblies and .NET framework.
- Before this was done it resulted in some confusing runtime errors about not being able to cast something to the original type (this is because it was the same type from two different versions of the assembly.)
- Updated references to obsolte methods
- Each obsolte method was flagged with a warning which specified which method to use instead. The latter was a very useful feature.
- Some of the namespaces for the datasets needed to be adjusted to include the subdirectory the dataset was in.
- Pretty straight forward once I figured out what it was referring too. Not sure why it worked before in VS2003.
Overall it was a fairly simple process. I didn't get a chance to use VS2005 much yet, but the one HUGE anoying bug or missing / changed feature was that chaning which file you were editing didn't update the location in the solution explorer. This resulted in manually hunting for the files in the solution explorer, which waisted a lot of time and was very frustrating. VS2003 has that feature, so I am not sure why they removed it from VS2005. Hopefully they fix that bug in time for release.
Tags: [Programming] [Software] [.NET] [Visual Studio] [.NET 2.0] [Visual Studio 2005] [Migration]
3 comments:
Currently my application is based on VS2003. If I move to VS2005, will the created application still work on .net 1.1 platforms?
Seshagiri
It is my understanding that VS2005 will do both .NET 1.1 and .NET 2.0. I'll check to make sure today though.
I checked into it, but forgot to post. It would appear that VS2005 only works with the 2.0 runtime. I was mistaken. It work with an assembly (as a reference) that was written for the 1.1 runtime, but any new assemblies will be 2.0
Post a Comment