VS 2008

Post by **jordansparks** » Mon Dec 31, 2007 6:07 am

I'll be looking into purchasing the VS 2008 upgrade today. Everyone else should do the same, or else be ready to use the new Express version when I make the announcement. I think I'm going to try for a side-by-side installation with VS 2005 so that only the head will move to the new format without affecting previous versions. We'll see how that works out. I'll make an announcement about the details after I do the final switchover sometime this week.

fcarlier · Post by **fcarlier** » Thu Jan 03, 2008 3:36 pm

For your information, the project files should be cross-compatible between VS2005 and VS2008: http://blogs.msdn.com/djpark/archive/20 ... -2008.aspx

You only need to maintain two different solution files, one for VS2005 and one for VS2008 for compatbility.

Hope it helps.

Post by **jordansparks** » Thu Jan 10, 2008 6:35 am

The head has been upgraded to VS2008. MS has a few versions available for immediate download. It's a huge download, and it's an .iso file. Which means you need to burn it to DVD in order to run it. Or, you can do like I did, and mount the iso file as a virtual DVD drive according to the instructions on the MS site. That worked fine.

If any one is interested in SilverLight for the new web version, they should install the SL 1.1 runtime, and then, the toolkit for VS2008, which was really hard to find. Hers's a link to the toolkit:
http://www.microsoft.com/downloads/deta ... laylang=en

I'm still working on getting a copy of Expression Blend.

Tom Opgenorth · Post by **Tom Opgenorth** » Sat Jan 12, 2008 6:41 pm

Just curious:

Are still sticking with .NET 2.0? Is there a plan/timeline for moving to .NET 3.5? I ask, because Mono doesn't have all of .NET 3.5 implemented, so a switch to the .NET 3.5 framework would have a negative impact on the Mono users.

Post by **jordansparks** » Sat Jan 12, 2008 7:47 pm

We are only using popular bits and pieces of later .NET versions which Mono does support. The build should continue to target 2.0, which I think we can specify in the solution/project properties.

But... as we move into SilverLight for the web version, I think we will have more freedom to use advanced features. I don't think we'll put any limits on what we do. The next few years will tell.