Last post Dec 14, 2006 09:41 AM by MartinS
Dec 11, 2006 10:09 AM|MartinS|LINK
Have been developing a web application in VS2003 for some time, and have just moved up to VS2005 (Standard Edition), and as my first migration project, ran the conversion wizard, which seemed to run OK first time. Went though and deleted all the OnInti
and InitializeComponent events, and had it all working perfectly by the end of day 1. Saved it all and closed up for the night, but next morning, when I opened the project again it asked me to convert it again, and so I let it run (not sure if I had a choice!)
and that conversion caused me lots of problems - firstly it moved all the aspx.cs files in the App_Code folder which then gave me 2000+ errors saying that so after going round the houses to fix those, I then had to move them all back. This was all a real pain
and took over a day of my time trying to figure out what it should have done.
I also do not have access to Web Application Projects (have posted about that in the appropriate section), so am not sure I am running the project in the best environment.
One thing I'm not sure about is source control - it stated during conversion that it was OK to have files under source control as long as they were not checked out to anyone else, but i did read somewhere else that all files should bve checked out before
migration takes place - can anyone confirm this for future projects?
Has anyone else had simlar problems or got any advice for converting existing 2003 projects to 2005 - I've seen the pages displaying the info on how to go about theses conversions but none mention the problems I've had.
Any help and/or advice gratefully received
Dec 14, 2006 09:41 AM|MartinS|LINK
Actually, all is OK - most of the problems were my misunderstanding of WAP integration into VS2005 [:$]