Quan To's Visual Studio Extensibility blog

The VS Beta and CTP uninstall tool has been updated and is now available at: http://go.microsoft.com/fwlink/?LinkID=47598 Please make sure you run this before installing any future version of Visual Studio 2005 (including the released version).

When trying to install the Release Candidate of Visual Studio (build 50727.26) on Windows Vista Beta 1, the installation will fail. The .NET Framework on Windows Vista Beta 1 does not match the .NET Framework packaged with The Visual Studio Release...

My intern this summer spent a couple of weeks writing a cool readme generator which takes bugs written using a specific template and generates the readme and known issues document we will ship with Visual Studio 2005. Last week, I spent a few hours...

Peter Marcu is one of our Setup devs on Visual Studio. He just launched his blog at: http://blogs.msdn.com/pmarcu/ Peter is our first developer on VS Setup to start blogging. That puts us at 4 total on our team :) Other blogs from VS Setup folks...

We're currently in the middle of an install blitz at Microsoft. The VS Setup team is trying to get 1500 internal folks to install a recent build. We're aiming to validate our Setup works correctly and at the same time find any potential show stoppers...

In case you were wondering, here's the list of supported operating systems you will be able to install Visual Studio 2005 on: Microsoft® Windows®° 2000 with SP4 Microsoft® Windows®°XP with SP2 Microsoft® Windows®°XP°Professional°x64°Edition°...

The company who ended up burning the PDC 2005 DVDs didn't realize the DVD Name on the media needs to be DVD1. The media table of the Visual Studio 2005 MSI requires the files to be on "DVD1" when installing from media. Since the label name is not DVD1...

As we get closer and closer to shipping Visual Studio 2005, we're making some tough decisions on what problems we can fix and what problems we'll punt and fix in Orcas. One such problem is when mscoree.dll is hard locked for write when you try installing...

Recently, we just fixed a nasty vertical integration / application isolation bug. The problem occurs when you: install the 1.1 SDK (using default installation path) install the 2.0 SDK (using default installation path) install any VS 2005...