One of the issues you will run into is that VS 2005 will take associations
away from 2003. i.e. if you double click a .sln file or any other VS
associated file, document invocation will default to 2005.
One of the issues you will run into is that VS 2005 will take associations
away from 2003. i.e. if you double click a .sln file or any other VS
associated file, document invocation will default to 2005.
It's possible this might occur the other way. If for some reason you
install 2005 first - or if you reinstall 2003 after you install 2005. The
last one installed will steal the file associations for itself.
I loaded the VS 2005 Preview on my PC and had problems when I went back to
VS 2003 and tried to run some -- not all -- but some projects in which
noting changed in the code but I got funky errors and the code would not
run. Help was all hosed then in VS 2003 as well.
I removed VS 2005 and VS 2003, rebooted and then reinstalled VS 2003 and was
good to go. I'll use VS 2005 on a seperate box and not on my main PC.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
