Printable View
I've just installed VS 2010 beta 2 on my machine and now I can't open up any vs2005 projects (in vs2005 IDE) without it coming up with the conversion wizard saying that this project was created in an earlier version of visual studio and must be converted. I cannot load the project without converting.
What's going on? I really don't want to convert it because...it shouldn't need converting.
Am I just going to have to uninstall 2010? :eek2:
are you double clicking on the sln file to open it? If you are, stop doing that. sln files have probably been linked back to VS2010....
If you are intending to open your 2005 solutions in 2010, then yes, it will need to be converted. the file layout has changed over time... even opening a 2005 project in 2008 will "convert" it... but it's all in the sln and vbp files... no actual code is converted. It should also ask if you want a back up when it does the conversion. I'm paranoid anyways, so I make my own backup copies of projects I'm upsizing.
-tg
I didn't make myself clear. I'm attempting to open a 2005 project in 2005 IDE. It still asks me to convert! Ever since installing VS2010 anyway...
I'm not certain, but I think I have seen this as well, even though I don't have VS2010. I assumed that it was something else causing it like a service pack. The conversion was always flawless, and I had no issues afterwards.
EDIT: To be clear, I saw the upgrade message when opening a VS2005 project in VS2005, just as you are seeing.
The VS version selector keeps track of that. I have VS 2003, 2005 & 2008 on my computers and I only ever double click the solution file to open projects and the version selector opens the correct IDE passing it the solution file path. VS 2010 should be no different, if it is, it's one more reason for me not to use it.Quote:
Originally Posted by techgnome
Like I said, I have had the same issue, and I have never installed 2010. So you can't just say that this is A 2010: chr(32) oddity.
I'm worried though that even if's ok afterwards on my machine that no one else will be able to open it after me (who haven't installed VS2010)...Quote:
Originally Posted by Shaggy Hiker
Oh well, I guess I'll just have to see...
Actually, it transpires that a reboot sorted it out! :blush:
Looks like sometimes the old remedies are the best! :thumb: