D'Arcy from Winnipeg
Musings of a Canadian Developer - Silverlight, ASP.NET, BizTalk, Life, and Technology
<< Why you need to look at SubSonic NOW. | Home | Feed Issues >>

.NET 2.0 Project in VS.NET 2005 != .NET 2.0 Project in VS.NET 2008

Thursday, November 22, 2007 8:36 AM

Interesting nuance with VS.NET 2008: although you can target a project for the .NET 2.0 framework, it seems that opening an existing project developed with VS.NET 2005 still requires you to go through a migration wizard.

When you think about it, this makes sense: the framework doesn't change, but the IDE does and as such the nuances for creating/reading project information.

So just be aware that if you create an app in 2008, and not all of your dev team has migrated up, they might not be able to access the projects.

D

Feedback

# re: .NET 2.0 Project in VS.NET 2005 != .NET 2.0 Project in VS.NET 2008

Mate,
The proj file does change when you run the upgrade wizard, it add some extra nodes in the xml. However VS2005 ignores those lines.

Its the solution files which are incompatible. But of course you can have more than one solution file accessing the same projects.

Therefore, create a new solution file that only upgraded vs2008 users use.
Then Add existing projects to the solution so that you can continue to work.
Your other colleagues that havent upgraded to vs2008 yet can still continue to use the original solution file.

You all share the same project files, but load with different solutions.

11/22/2007 9:37 AM | MarkK

# re: .NET 2.0 Project in VS.NET 2005 != .NET 2.0 Project in VS.NET 2008

Yup, just copy your VS2005 solution, open the copy in 2008 and now you have an upgraded solution + the old solution. That way you can have devs using VS2008 and VS2005 both work with the projects.
Of course, if you add new projects, both solution files need to be updated, but that's not too hard. 11/22/2007 9:38 AM | Aaron

# re: .NET 2.0 Project in VS.NET 2005 != .NET 2.0 Project in VS.NET 2008

When you throw source control into the mix that seems like adding extra work though (managing two sets of solution files). Probably easier to just

a) use one solution file since, as Mark mentioned, VS 2005 will just ignore the extra nodes (and hopefully not blow up?)

or

b) just upgrade everyone to 2008 anyway.
;)

D 11/22/2007 9:43 AM | D'Arcy from Winnipeg

# re: .NET 2.0 Project in VS.NET 2005 != .NET 2.0 Project in VS.NET 2008

Its the extra stuff in the project file that vs2005 ignores, the solution file cannot be shared between the 2 versions.

We (unfortunately) still use sourcesafe for our version control. but we never have the solution file controlled in vs. That gives each developer the freedom to load/unload different projects, without having to check out, etc.

11/22/2007 11:20 PM | Mark
Post a comment





 

 

News



Disclaimer
The views expressed on this weblog are mine and do not necessarily reflect the views of my employer.

All postings are provided "AS IS" with no warranties, and confer no rights.

Twitter












Tag Cloud


Archives

Central Canadian UG's

Gamertag

Ignite Your Life

Peeps

Sites

Winnipeg Code Camp

Syndication:

 
© 2007 Website.com. Valid CSS & XHTML Website template by Arcsin adapted by timheuer