http://blogs.msdn.com/b/visualstudio...-projects.aspx
I tried reading that explanation and wasn't totally convinced. Can anyone explain what technical reasons prevented Microsoft from allowing VS2010 to open VS2008 projects without conversion?
Printable View
http://blogs.msdn.com/b/visualstudio...-projects.aspx
I tried reading that explanation and wasn't totally convinced. Can anyone explain what technical reasons prevented Microsoft from allowing VS2010 to open VS2008 projects without conversion?
The way I understand it is that VS2010 uses different set of referenced files than those of VB2008 that is why it needs to convert the code.
I could understand that for a project in the VS2010 project format, but I still can't see why VS2010 wouldn't be able to open a VS2008 project file.
Microsoft Office has handled legacy formats for years without requiring conversion to the latest document format.
I would think that would be the same reason. I found this as one of the responses to the article:
Edit:Quote:
Visual Studio Converter 2010 to 2008
CVSVC is Windows utility for converting between Visual Studio 2010 Forms Project to 2008 version İts supports only Visual Studio 2010 and convert only Windows Form Projects. Original version of the code was created by Mezo Powered by Crewel
Download Link:
http://hotfile.com/dl/55611070/65372...erter.rar.html
I don't know if this will help explain things.
Backward compatibility is always a ball and chain. They could have chosen to support backward compatibility but it would have made implementing some of the desired features more difficult or impossible. There's something to gain and something to lose either way. They chose to go one way and not the other because they thought there was more to gain and less to lose that way.
And look at all the baggage that they've had to drag along to make that happen, and all the criticism they've received as a result. You'll never please all of the people all of the time. Round-tripping is something that I don't personally need, so I'm happy that they chose not to support it for the benefits in other areas.
Maybe because in VS2010 you can do things (eg target to .net 4.0) that can't be done in 2008, so the sln won't work in 2008...