Click here to Skip to main content
15,900,818 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I have just started a project where teh existing codebase is all in VS 2008 ... My dev machine and entire lab is on 2010 - can I safely stay on 2010 and integrate with their dev team or am I just asking for a headache and do i need to DOWNGRADE? ugh
Posted

See http://social.msdn.microsoft.com/Forums/da-DK/vsprereleaseannouncements/thread/dae62b32-f526-41a2-9878-78ecb338ff8c[^]

If you continue to target the .NET 3.5 framework, you should be OK with the code files. The problem is that the VS 2010 conversion tool changes the project files.

So you would need to have two copies of the project file(s), ones that you use and ones for VS 2008.

Hope this helps.
 
Share this answer
 
If you only use C# .NET code in your project and not other 3rd party assamblies or dependencies, it is a good choice to update to Visual Studio 2010 and .NET 4.0.
 
Share this answer
 
Comments
Philippe Mori 30-Sep-11 20:32pm    
And since VS 2010 supports multi-targetting, it might be a good idea anyway... except maybe for those that are doing C++/CLI since Intellisence was not available in that version. At least, it is available in VS 11 Preview and it works better than it was working in VS 2008.

Well if you have a slow computer, an older version might be a bit faster... but on adequate hardware, VS 2010 works smoothly.
For my application, I have tried to do maintenance (fix bugs and do some improvement) of the current version in VS 2008 using .NET 2.0 and do main development using VS 2010 and .NET 4.0.

But with time, differences were accumulating so in the end, I decide to do all developement in VS 2010. I have taken the VS 2010 projects, target them to .NET 2.0, remove the stuff not ready for release and take that for maintenance.

Since I have done that, it is much easier to keep projects in sync when bugs are fixed or some minor improvement are done for the released versions. In fact, I use PureCM for source control and most of the time, changes are automatically merged (but this does not work well for auto-generated files when we need to keep some difference as often the auto-generated code is not very stable).

A good new is that VS 11 Preview is able to open VS 2010 projects and vice-versa.

In my case, it was also problematic because the format of C++ projects has changed...
 
Share this answer
 
Comments
jkeelerz 30-Sep-11 19:39pm    
what types of differences were accumulating? See, I do NOT have the option to upgrade their codebase or versions... so do you think I may have to downgrade my devenv?
Philippe Mori 30-Sep-11 20:29pm    
You can always give it a try... There are so many possibilities depending on what your are using (Datasets, reports, Linq, Settings, Ressources...), which version of .NET you are targetting, the kind of changes you will made, the complexity of the UI.

If changes are mainly user code (in existing files) then it should not be too much of an issues.

On the other hand, if your project are modified a lot, then maintaining both of them up-to-date might not be effective as an example.... and VS 2010 users would then have to use VS 2008 to update projects for the other groups and vice-versa. Well they might be modified by hand but then without having Visual Studio, how do you ensure nothing is broken?

If you have regular automated builds on a server, then it might not be an issue but this all depends on how your teams works.

In my case, I was working stand-alone and I have both VS 2008 and VS 2010 installed... but now that the conversion has been made including on the maintenance branch, I do not use VS 2008 anymore. Most of the time, I am using VS 11 Preview.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900