Visual Studio 2003 to VS 2005 solution conversion
As from 7th of November I'm trying to covert and test my existing VS 2003 solutions into VS 2005. I've made some test conversions while on beta phase but I hadn't tried it on really big, real word solutions. Here are some of the problems I've encountered:
- Datasets with unknown data type declarations for table fields: VS 2003 allowed that. I've seen a table field with the data type "bit", entered by mistake. VS 2003 didn’t show up a single warning, and the build didn’t have a problem also. While converting the project though, VS 2005 refuses to convert this dataset.
- Large scale mess-up with assemblies references of crystal reports: While converting a solution with a large number of crystal reports, the references went crazy. Removing and re-importing the dll references didn’t help at all.
- Extensive mess-up with project references in web projects: The web projects are quite different in the new VS. If your web project contains a large number of project and external dll references, before converting your web projects move all your code-behind code to a separate project.
If you have big trouble converting your solutions too, maybe the following procedure will help:
- Create a new solution and add your old projects one at a time, starting with the projects that are lower in the dependence hierarchy. Write down every single problem you encounter, try to fix it temporarily and go on to the next project.
- Throw away your converted solution; go back to VS 2003 and do all the necessary fixes you wrote down at the previous step.
- Do the first step once again. (One project at a time)
That's for now; I've not done with my conversion yet. I'll post here any further experiences...