Administrators 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.
Administrators 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,
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.
Now 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,
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,