views:

284

answers:

3

I have a project on SourceSafe that the team work with VS 2005.

I have installed VS2010 and like some features of this version.

Is there a way that I keep the project to day with SourceSafe, but however work locally with VS2010.

Say, I could not add new files to solution, but at least obtain, modify and archive the existing ones.

+1  A: 

You can update all of the source files pretty safely unless you're adding code that is new since VS 2005. The main difference between the VS versions is in the project, and the solution files. What you can do is make your local project and solution files writable, and then use your source control to modify the source files. When all is said and done though you'll want to build it in 2005 (with the SourceSafe versions of the project and solution files) to make sure it all still works.

Also note that the conversion utility in Visual Studio that converts projects from previous VS versions is only intended to convert projects from the previous version. Since VS 2010's previous version is VS 2008 and not VS 2005 you may have to perform manual changes on your solution and project settings to get everything to build. The main thing that comes to mind is how global include directories are handled. If you have access to VS 2008 convert it to that first, and then to VS 2010.

Ben Burnett
VS converted without problems project and solution files from 2005 to 2010.
serhio
Excellent. As long as you don't check in the project and solution files you should be okay to check any other changes you make in. Just get your team to switch to VS 2010 now, and you won't even have to worry about that.
Ben Burnett
Switching the team is not so easy. There are other projects linked, so converting them all to VS2010 could be a little time consuming. And also VS2010 has some strange bugs, by e.g. it does not recognize installed CrystalReport references...
serhio
A: 

You should be very careful NOT TO USE new syntax features introduced in VS2010. There are many of them that make coding less tedious, but they are not available in VS2005. For example, property declaration - can be done in VS2010 in one line with no Getter and Setter explicitly declared (not applicable to ReadOnly properties though).

Anvar
the problem is not in the new syntax declaration, but in source safe binding.
serhio
and also, if I target the framework to .NET 2 VS I believe will take care of the used syntax.
serhio
A: 

Besides targetting the 2.0 framework VS2010 will still let you use new language features so you have to be careful.

And as Ben Burnett said, the sourcesafe binding doens't have to be a problem as long as you don't check out project and solution files. You can remove the read only flag from them so VS2010 can edit them, but they don't need be be checked into sourcesafe.

But I really wonder which feature you like so much about VS2010 that you want to restrict yourself to not be able to add, remove or rename files from your project.

LeonG
I have installed both VS 2005 and 2010, but 2010 is more "friendly". :) So as I don't remove or add new files very often, I can do it with "normal" 2005, but edit the code with 2010.
serhio