views:

9481

answers:

6

Does anyone know if VS2010 will use the same project & solution file format as 2008, or will the 2008 project files need to be upgraded to 2010 format before they'll open in that version?

+1  A: 

VS2010 is going to be able to handle 2.0 through 4.0 framework projects, so if you have a project in one of those frameworks, it is unlikely that you would have to worry about any sort of updates or imports or anything of that sort to get up and running with current projects.

TheTXI
I'm not seeing that.
Jonathan Allen
ya, that's a very generalized statement and won't work for everyone. For example, when working with large teams you can't force everyone to upgrade to VS2010 just because one developer did. There's licensing considerations also...
Dave
+8  A: 

"Visual Studio 2010 will allow you to move your projects from previous versions of Visual Studios to VS 2010 with ease, I will call this process as “Converting” the project from VS 200X to VS 2010…

VS 2010 will also allow you to change your project’s Target Framework Version to .NET 4.0 from .NET 2.0, 3.0 or 3.5… I will call this process as “Upgrading”…"

extracted from http://vishaljoshi.blogspot.com/2009/05/vs-2010-project-conversion-upgrade.html

João Guilherme
That's a bummer. They did the same with 2005/2008 projects - made it tough to work on the same project in different versions of studio for testing.
Scott Ivey
VS 2005 could read VS 2008 project files, so you could have just created new solution files. I am hoping that I can get away with the same trick in VS 2010.
Jonathan Allen
For C# projects, a VS2008 project file had to be modified in order for VS2005 to read it. A minor modification, but still a modification.
John Saunders
He's talking about keeping the older VS 2008/2005 project and .sln and other files from being upgraded but still work with them in vS 2010.
CoffeeAddict
+5  A: 

There is a trick.

  1. Create a new Solution file.
  2. Add all the existing projects, upgrading them in the process.
  3. Use the old solution file in VS 2008 and the new one in VS 2010.

I did the same thing with VS 2005/2008 and didn't run into any problems.

Jonathan Allen
That doesn't solve the problem if the project files are under source control and the rest of the team is using VS 2008.
Richard Hein
VS 2008 can read VS 2010 project files. It just can't read VS 2010 solution files.
Jonathan Allen
Better yet, instead of creating a new solution file, just copy the original one. Rename them to indicate which is 2008 and which is 2010. Then open and upgrade the 2010. The 2008 one will still work with VS 2008, even though the projects in it have been "upgraded".
Kyralessa
+3  A: 

You could just have two different solution files. Usually in open source they make fx. project-2008.sln and project-2005.sln.

TigerShark
simplest solutions are always the best!
Cornelius
doesn't help if the projects were created in VS2010,
Dusty Roberts
+5  A: 

Well, there's a problem actually that you'll run into if you try to open a VS2010 project on a computer running only VS2008.

VS2010 makes changes to a MSBuild reference (.target-file) in the project file, and it can not compile in VS2008 if you don't change that reference back to the VS2008 default. But if you have both versions installed on the same machine it will work just fine.

So, you can have half you team install the VS2010 version without ever using it, and they can use VS2008 for whatever reason they want to.

I'm unsure however how language specific feature to release 4.0 of the framework will work with VS2008, my theory is that the IDE won't take it all to well. So if you use C# but target both VS2008 and VS2010, avoid the new language features.

John Leidegren
+4  A: 

I've just created a little batch file that will convert between VS2008 and VS2010 (vice versa) at will. Grab it from: http://bit.ly/9cwEDI

It rewrites the strings found at http://blogs.msdn.com/rextang/archive/2009/07/06/9819189.aspx between both versions in an automated fashion.

sebastiaan