Visual Studio Setup

Installation and containerization of the Visual Studio family of products

.NET Archives - Visual Studio Setup

Announcing Visual Studio 2012 Release Candidate

May 31, 2012 May 31, 2012 05/31/12
Heath Stewart
Microsoft Visual Studio 2012 Release Candidate (RC) – formerly known as Visual Studio 11 – is now available for download! Jason Zander’s blog has a lot of great information on all the exciting changes we have made, including improvements to setup. I encourage you to download and give VS2012 RC a try. Should you find any ...

Introducing Managed Bootstrapper Applications

October 28, 2011 Oct 28, 2011 10/28/11
Heath Stewart
Now that WiX v3.6 has been released, I introduce the managed bootstrapper application (MBA) interoperability layer. It’s been available for a while actually, and if you’ve installed any builds of WiX v3.6, or the Microsoft Visual Studio 11.0 Developer Preview you’ve seen it in action. While Burn – the WiX bootstrapper engine – and...

Detection keys for .NET Framework 4.0 and Visual Studio 2010

May 4, 2010 May 4, 2010 05/4/10
Heath Stewart
Now that Microsoft .NET Framework 4.0 and Visual Studio 2010 have been released, developers may wonder how to detect them on the system. As with previous releases, we support registry detection of either product family and Windows Installer component detection for Visual Studio. Detecting either product uses a separate set of supported keys. ....

Microsoft .NET Framework 4.0 RC and Visual Studio 2010 RC Available Now

February 10, 2010 Feb 10, 2010 02/10/10
Heath Stewart
Announced yesterday for MSDN subscribers, the Microsoft .NET Framework 4.0 and Visual Studio 2010 Release Candidates are available today for everyone to download.Feedback on VS2010 RC has been great, and we hope you agree. Feel free to provide feedback about your installation and development experience. Performance was a major focus for the RC...

Visual Studio 2010 and .NET Framework 4 Beta 2 Released

October 19, 2009 Oct 19, 2009 10/19/09
Heath Stewart
As announced on Soma’s blog this morning, Microsoft Visual Studio 2010 Beta 2 and the .NET Framework 4 Beta 2 have been released to MSDN Subscribers and will be available for everyone on Wednesday.Visual Studio 2010 boasts a great new user interface with better contrast and lots of UI elements that tend to add confusion to the ...

Microsoft .NET Framework 4.0 Beta 1 should be removed before upgrading to Windows 7

August 9, 2009 Aug 9, 2009 08/9/09
Heath Stewart
If you have been beta testing Microsoft .NET Framework 4.0 Beta 1, we recommend you install a fresh copy of Windows 7 on your machine. Alternatively, you may also choose to uninstall Visual Studio 2010 Beta 1 and .NET 4.0 Beta 1 prior to upgrading to Win7.Microsoft Windows 7 is available to MSDN and TechNet subscribers.ProblemIf you have ...

Detecting Visual Studio 2008 Service Pack 1

May 29, 2009 May 29, 2009 05/29/09
Heath Stewart
The Visual Studio 2008 RTM and SP1 detection keys are largely the same as the Visual Studio 2005 SP1 detection keys, and are documented below. But there is a caveat for released and upcoming versions: the shared detection value can be overwritten by an older installation of the same release.For example, if you installed VS2008 Professional, ...

Updated log collection utility available for Visual Studio 2010 and .NET 4.0 Beta 1

May 22, 2009 May 22, 2009 05/22/09
Heath Stewart
Last Monday we shipped Visual Studio 2010 Beta 1 and .NET Framework 4.0 Beta 1 to MSDN customers, and made them publicly available Wednesday. More information about Visual Studio 2010 and .NET Framework 4.0 are available on MSDN, and Aaron Stebner has a good collection of direct links.While we have worked hard to reduce install times and ...

Microsoft VS/.NET Log Collection Tool

May 20, 2009 May 20, 2009 05/20/09
Heath Stewart
Using the Collect Utility If you encounter any setup issues, we will need all relevant logs. Please follow the instructions below to collect all those logs. Reporting Setup Errors There are several options for reporting setup errors, but you might consider first checking to see if the issue is a known issue. This will save you time and ...