Hi,
Solution files are not compatible, but project files are. So you could have two diffrent solution files and keep all projects the same.

(it is mentioned in the comments in ScottGu's blog announcing the release)

Kay

Hey Thanks! Thats great news I'll give it a try.

Joe

The only difference in the .sln file is the solution version 9.0 or 10.0.  Project files are compatible.  I converted a VS2008(.Net 2.0) solution back to VS2005 by changing the first line of the .sln file back to "9.0". 

If you have developers using 2005 and 2008, provide two .sln files that pull in the same projects.  The project files don't need to be different, only the .sln file.

Just wait for Mono ASP.NET API status ;)

It should support 3.5 API next year.

This is great . I was going to email you about this very thing, having just finished my download of VS2008.

I guess, it's more important to keep pace with Mono as far as possible. There's  a temptation to use the new 3.5 features, but  in my opinion it's more wise  to focus on supported features and security now. No matter what VS version will be used, more important is that only supported features should be implemented, if possible, of course.

Hi Bob,

Yes, don't worry, I have no plans to leave behind Mono. If I build anything that targets 3.5 before Mono supports it I will do it in separate projects so the core can stay compatible with Mono. Cross platform support is a very improtant a goal for the project.

Cheers,

Joe

I have some experience in these matters from my "earlier life" working on SmartWin++ and it's not really that hard, though pretty annoying... :(

SmartWin++ compiles on both VS2003 and VS2005 and those two can mostly run side by side. I assume the same is true for VS2005 / VS2008...
So if you first install VS2003 and then VS2005 ALWAYS in that order you will be able to run them side by side and supply two different set of .sln files (and .vcproj files if that format has updated) then you just make sure that the code is compatible with C# 2.0 always and if you need C# 3.0 features (which you never need mostly) you just use #if conditional compiler statements...

Then you supply two binary versions of your library, one compiled for .Net Fr. 3.5 and another compiled for .Net Fr. 2.0...
Normally the SAME NAME of the DLLs (exes...?) but in different FOLDERS...
And off course since I assume this is an OS project the code will be there for those that modifies it :)

A little bit of hassle, but worth it to keep backwards compatibility during the "transition of power" which hopefully will be over within a couple of years :)

This solution will also make sure you'll not build from features currently not supported in Mono too :)

Cheers,

Thomas

Not sure about the US, but here in the UK the hosting providers take ages to update their .NET framework support after each revision. Not much point using new technology if you're unable to host it. Might be an idea to wait for better 3.5 support.

Cheers,

Reiss

Before the vs2008 lovefest begins, I noticed from the svn checkout that the vs2005 solution file does not open successfully. It appears to be using files that were installed by 2008, and so if those are not present the files will not open.

As an example to highlight this point, PollFeature.UI.csproj line 178:

<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\WebApplications\Microsoft.WebApplication.targets" Condition="" />
 

This refers to a file only found in the vs2008 installation.

Thanks for letting me know, I'm looking into this now. I think I must have done something configuring projects that caused this. Note that I have been opening mojoportal-core-vs2005.sln in VS 2005 all week on my load testing machine. Since this contains a web project obviously there is compatibilty between the projects in VS 2005 and VS 2008 but I am getting the same error you mention when I try to open mojoportal-complete-vs2005.sln so something happened to the additional web projects that did not happen to the main one. Probably due to me monkeying around in the project property pages in VS 2008.

I'll get this figured out and fixed asap, but in the meantime you can open mojoportal-core-vs2005.sln using VS 2005 SP1

Thanks again for letting me know.

Joe

This is now fixed in svn trunk, if you do svn > Update it will pull down the new files and the soltion will open and build in VS 2005. The VS 2008 solutions still work fine as well.

Thanks Again for pointing this out as I had not noticed it since only opening the core solution recently in VS 2005.

Joe

I've just completed a utility that will allow you to convert between VS2005 and VS2008 projects. (It just edits the solution and project files... no other conversion is done). 

I'd consider it an "advanced beta", but folks are welcome to take a look at the VB2008 source code.

http://home.hot.rr.com/graye/Temp/ProjectConverter.zip