I had it installed and VS6, VS.NET02, and VS.NET03 worked fine with eachother. IIS is the one that crapped out, so I had to uninstall after 2 months.

I've got VS6, VS2002, VS2003, and Whidbey all working together just fine, and they've been working fine, with IIS too, for a good 4 months now. Its all on an XP Pro laptop, along with SQL 2000 and Yukon too. The only problems I've had has been Yukon's Enterprise Manager in some cases. Of course, this is all my personal laptop -- I wouldn't put all this on a corporate machine.

Ditto. On my desktop at home, I have VS6, 2002, 2003 and Whidbey.

There are a couple of quirks, but every one that I've run into has been explained by the ReadMe, and been fixable.

::Will Whidbey coexist with VS.NET 2003?

No, it WILL not - it DOES. Already.

Be sure to install the latest MSDN Library, if not you will have problems with the help in VS2003.

Is there a way to share projects/solutions between the two? I'd like to develop on Whidbey and use VS.NET '03 for final builds against the 1.1 .NET Framework. If there's not, my next question is "Has anyone got MS Build to work on Server 2003/VS.NET '03?".

Cheers,

Steve

The real question (which you ask) is do you dare put it on your dev machine. I wouldn't. It's alpha software. Why even consider the risk?

No, the solution files are in different formats. So, when you open a VS.NET 2003 solution in Whidbey, it will upgrade it for you.

Also, to get multiple frameworks asociated with different virtual webs (running different .NET Frameworks side-by-side) you'll need to do some manual configuration (by default, all IIS virtual webs are associated with the .NET Framework version that was last installed). I wrote a blog entry on how to do this manual configuration at: http://www.ddconsult.com/blogs/illuminati/archives/000164.html

Julie,

You bring up an interesting point. I consider a Dev machine used to develop production code a production machine. So, you really need a development machine that is dedicated to alpha/beta software evaluation, testing and general developer future looking (you know developers need to be given time to take a look at new technologies so that they can decide whether it's something to use in production later on).

I would use VMWare or Microsoft Virtual PC. Install either on your laptop and set up a virtual operating system. Install Whidbey on this virtual machine and try it out in a safe environment. While many others commenters have noted no problems, why take the risk. Alpha software is risky and can go through many changes before shipping.

Doug,
I agree completly... I actually already have a beta box which has longhorn. I also have a development desktop and a development laptop. I switch between the two depending on where I'm working. If I hose the laptop, I'm not out of luck, I can rebuild it and work on the desktop for the time being.

Thanks for the link to running different vwebs, I'll read it today b/c I'm going to do the whidbey install tonight! ;-)

So now I need to rename my boxes I guess!

My reference to "dev" machine is the one where I am doing all of my production work. So that's the one that I am saying "no way" on - which Doug was asking about : "one that pays the bills"

I have whidbey on my laptop alongside of VB6, .net 1.0 and .net 1.1. I may put whidbey on my tablet if I choose to use my tablet for my next presentations.

Julie,

Why rename your boxes just for me? :)

In all seriousness, though, I've visited a lot of shop and the term "dev machine" means different things to different companies. I, like you, tend to use "dev machine" as the one that pays the bills, and a "beta machine" as the machine to evaluate and test products. Like you, I also run Whidbey & Yukon on a laptop running Windows Server 2003, while my dual-proc dev machine just has VS.NET 2003 for my primary development and code for articles.