Last post Jun 12, 2008 06:21 AM by MartinS
Jun 09, 2008 10:08 AM|MartinS|LINK
I have done a few of these now, and after following many threads on the subject, found that creating a brand new solution, and then adding converted files to the solution appeared to be the way to get a conversion to work properly...well, until today that
I have a ASP.NET Web Project written in VS2003, which I wanted to convert to VS2005. Here are the stages I went through:
Take a copy of .NET2003 solution, and run it through the conversion process in VS2005.
Create a new ASP.NET Web Project, and add in the required library folder.
Copy over any dlls required to the library folder and add them as references.
We have an odd folder layout for out projects whereby you create a project and the code lives in a subfolder called WebCSharp, so after creating a new project, I then modify the SLN file to point to WebCSharp\Solution.csproj.
I then import all the aspx pages from the converted project above, and then run 'convert to web application projects'.
I then go through and remove the resx files.
Lastly, I copy the converted files over my source controlled sandbox, add in the designer files to source control and that should be it.
It seems to continue to work quite happily for me, but as soon as my another team member resynchs their sandbox for the project, and opens it in VS2005, that's where the problems start.
what is does is change the project name in the solution explorer to it's location, and then loses all the references, making the project unusable. It seems to be the GUIDs in the soluition file that keep changing from machine to machine, and i don't know
what makes them change. My team member and I both have the same sandbox location, and the same version of VS2005, so am not sure what it is that is breaking it. If anyone can shed some light on this it would be most appreciated.
Jun 12, 2008 05:51 AM|Thomas Sun – MSFT|LINK
In your case, you don't need to create new solution to convert the page to Partial Classes using "Convert to Web Application".
You can try to temporarily remove/unbind solution from source control prior to converting it. Once converted, you can then add it back under source control. You had better not modify the solution file manually.
You can following
If you convert it completely, you need to check in all the files such as project file to source control.
I hope this helps.
Jun 12, 2008 06:21 AM|MartinS|LINK
This was an odd one as have done several already, following pretty much the process you link to above, but it just didn't work.
I got there eventually by going through the process again and it seemed to work. Not sure why it wouldn't work for the other 5 attempts we made, but it's sorted now - hopefully that is the last 2003 application we have!
I do hope that when rolling from 2005 to 2008 there isn't a whole load more problems to deal with!