This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn More
Installation and containerization of the Visual Studio family of products
April 13, 2015Apr 13, 201504/13/15Administrators and developers who need to detect whether Visual Studio 2015 is installed can use similar registry keys as with past releases. This time around, though, we’ve made some changes to the lineup of products but the registry scheme remains the same.
August 3, 2012Aug 3, 201208/3/12Administrators and developers who need to detect if Visual Studio 2012 is installed on a machine can use similar keys as those used for past releases like Visual Studio 2010. In general, these detection keys are always found in the 32-bit registry hive with a pattern like:
Core product: HKLMSoftwareMicrosoftDevDivFamilyServicingVersionEdition
Installed languages: HKLMSoftwareMicrosoftDevDivFamilyServicingVersionEditionLCID
So if you needed to detect if VS2012 Ultimate is installed,
May 4, 2010May 4, 201005/4/10Now 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.
May 29, 2009May 29, 200905/29/09The 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.
November 26, 2007Nov 26, 200711/26/07No doubt you’ve heard the Microsoft .NET Framework 3.5 was released. Aaron Stebner has posted a list of links to 3.5, as well as 2.0 Service Pack 1 (SP1) and 3.0 SP1. It’s important to note that if you install 3.5 you’re actually getting 2.0 SP1 and 3.0 SP1 both.
December 17, 2006Dec 17, 200612/17/06Now that Visual Studio 2005 Service Pack 1 is released, it can be detected programmatically in various ways. Registry detection is recommended for ease and is less impacted by future changes to the product installation. Because there are many different Visual Studio 2005 editions and service pack 1 patch packages,
April 7, 2006Apr 7, 200604/7/06Aaron Stebner
posted
some sample code to detect whether the .NET Framework 1.0, 1.1, or 2.0 were
installed and at what service pack level they are. Basically, the .NET Framework
installation writes a common, version-specific registry key in the following
location along with an SP level registry value.
