Follow me on Twitter at Twitter.com/wbm
FYI, I'm blogging most of my stuff over at More Wally now.
You might want to add my rss feed to your reader at:http://morewally.com/cs/blogs/wallym/rss.aspx
Working with various builds of .NET 2.0 Whidbey Framework - Wallace B. McClure

Wallace B. McClure

All About Wally McClure - The musings of Wallym on Web, HTML5, Mobile, Xamarin.iOS, Xamarin.Android, and Windows Azure.

News

Visual Studio Magazine Column Personal Blog

.NET

Book Authors

Business

Family

Friends

Georgia Tech Bloggers

Personal

Archives

Working with various builds of .NET 2.0 Whidbey Framework

I am familiar with several different builds of .NET 2.0 Whidbey that are currently running around.  These are listed below along with what I think the build numbers are:

  • Beta 1 of Whidbey / Beta 2 of Yukon.  These bits are from July and are a set that go together. (Build 40607.X)
  • September CTP of Team Studio.  (Sorry, I don't have the build number, think it was 40607.85)
  • October CTP of Sql Server 2005. (Build 40903)
  • November CTP of Visual Studio.  (Build 41202)
  • December CTP of Sql Server 2005.  (Build 40903.27)

Each team is on a slightly different schedule, so each team is putting out bits that have different build of .NET 2.0 Whidbey Framework. It has been my finding that these builds can't be mixed and matched on the same machine.  So, how should you get things working?  Well, you have a couple of alternatives.

  • VirtualPC or VMWare allow you to run virtual PC Sessions.  You can setup Win2k3 Server, Windows XP, or Windows 2000 sessions that can allow you to play with the bits without mucking your base machine.  Make sure that you make a copy of your Guest OS, before you install a build of .NET, that way, you can start over when you need a fresh machine.
  • Multiple machines.  I know everyone has multiple machines laying around with upto date processors and at least 512 megs of ram.
  • Uninstall/Install.  Just run install/uninstall each time you want to play with a different tool, wow is this option dangerous.
  • Some other option I am not familiar with.

The bottom line is that these various builds are not going to work and play well together (at least they don't for me), so, if you want to work with multiple copies of them, you are going to have to figure out a way to make them work and play well together.

I hope that this has been helpful.

Wally

PS.  Sorry if this was a repeat, but I keep getting and seeing this question run around. 

Comments

Mike Lorengo said:

Hmmm, What's v.2.0.41202, that's what I got when I downloaded the November CTP of off MSDN...
-=mike
# December 20, 2004 6:53 PM

Drazen Dotlic said:

Hey,

thanks for summarizing. I am really irritated by this multiplicity of .NET versions. My primary concern is that I do not want to run two virtual machines to get SQL Server (NOT Express) and Visual Studio, but looks like I'll have to for the foreseeable future. Oh well...
# December 21, 2004 6:16 AM

Snorrk said:

Here at Reykjavik University there is a bunch of up-to-date machines with plenty of RAM.

The problem is remembering which machine hosts which version of VS.2005...
# December 21, 2004 7:18 AM