Thursday, 22 November 2007

Visual Studio 2008 RTM - First impressions

I haven't done heaps with 2008 since installing it yesterday.

I did investigate opening one of our existing projects to see if I could create a 2008 solution, while leaving the 2005 solution intact so that other people could still use 2005 to work on the code. I'd read that this is possible.

I struck a problem though - it looks like this strategy doesn't work for web applications projects.

The upgrade wizard modifies the path in the project file to where the web application project msbuild stuff gets included from. This would obviously not work for other team members who didn't also have 2008 installed on their machines.

So it looks like the best plan is to make sure everyone on the team starts using 2008 at the same time.

I also need to confirm that all our various addins and dependencies also continue to work - things like PageMethods and ActiveWriter are good examples.

It is nice to have the IDE start without requiring it to run in Admin mode on Vista though.

1 comment:

Jason Stangroome said...

I wrestled with sharing projects between VS2005 and VS2008 a couple of weeks ago and hit the same stumbling block. Web App projects, DB Pro projects, VSTS test projects, all end up with different dependencies. Stick to class libraries and Windows App projects and you might be ok.

We've bitten the bullet and dropped VS2008 onto all machines.

- Jason