вторник 25 февраляadmin
HOWTO: Detect installed Visual Studio editions, packages or service packs

Author: Carlos J. Quintero (Microsoft MVP)Applies to:Microsoft Visual Studio 2005
Date: February 2008Microsoft Visual Studio 2008
Updated:December 2014Microsoft Visual Studio 2010
Microsoft Visual Studio 2012
Microsoft Visual Studio 2013
Introduction

Everything else looks like variable, function names, enum members, defines. Microsoft Visual Studio 2005 Professional Edition - ENU Service.

This article explains how to detect programmatically (from inside an add-in or package, or from a setup) which Visual Studio versions (2005, 2008, etc.), editions (Standard, Professional, etc.) are installed and whether a specific package (subsystem) or service pack is installed or not.

Note 1: Visual Studio Express editions don't support extensibility (add-ins or packages).

Note 2: The official way provided by Microsoft is described at Detecting System Requirements (ensure to select the desired Visual Studio version).

Detecting Visual Studio versions, editions and packages from a setup

  • To detect which Visual Studio versions (2005, 2008, etc.) are installed on a computer from a setup, you can use the following Windows registry entries (or the ones in the next section):
    • For Visual Studio 2005: HKEY_CLASSES_ROOTVisualStudio.DTE.8.0
    • For Visual Studio 2008: HKEY_CLASSES_ROOTVisualStudio.DTE.9.0
    • For Visual Studio 2010: HKEY_CLASSES_ROOTVisualStudio.DTE.10.0
    • For Visual Studio 2012: HKEY_CLASSES_ROOTVisualStudio.DTE.11.0
    • For Visual Studio 2013: HKEY_CLASSES_ROOTVisualStudio.DTE.12.0
  • To detect which specific editions (Standard, Professional, Team Edition, etc.) are installed on a computer from a setup, you can use the following Windows registry entries:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio<version>SetupVS<edition>
    Where <version> can be:
    • For Visual Studio 2005: 8.0
    • For Visual Studio 2008: 9.0
    • For Visual Studio 2010: 10.0
    • For Visual Studio 2012: 11.0
    • For Visual Studio 2013: 12.0

    And <edition> can be:
    • For the Standard Edition: Std
    • For the Professional Edition: Pro
    • For the Team Edition for Software Architects: VSTA
    • For the Team Edition for Software Testers: VSTT
    • For the Team Edition for Software Developers: VSTD
    • For the Team Suite Edition: VSTS
    • For the Premier Partner Edition (2005) or Shell Edition (2008): IDE
    • For the Visual Studio 2005 Tools for the Microsoft Office System: VSTO

    Furthermore, the 'ProductDir' value sets the installation folder.
    Note: the Express Editions don't use the HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio registry key but the following ones:
    • For VB Express: HKEY_LOCAL_MACHINESoftwareMicrosoftVBExpress
    • For VC Express: HKEY_LOCAL_MACHINESoftwareMicrosoftVCExpress
    • For C# Express: HKEY_LOCAL_MACHINESoftwareMicrosoftVCSExpress
    • For J# Express: HKEY_LOCAL_MACHINESoftwareMicrosoftVJSExpress
    • For Web Developer Express: HKEY_LOCAL_MACHINESoftwareMicrosoftVWDExpress
  • To detect whether a specific Visual Studio package is installed or not, you need to know ifs unique identifier (GUID) and use the following Windows registry entry:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio<version>Packages<Package Guid>

Detecting Visual Studio versions and editions from an add-in or package

Add-ins and packages can detect the version, edition and installed packages of the IDE where they are loaded:

  • To detect which Visual Studio version a (multi-IDE) add-in is running under, you can use the EnvDTE.DTE.RegistryRoot property, which can return the following values:
    • For Visual Studio 2005: SoftwareMicrosoftVisualStudio8.0
    • For Visual Studio 2008: SoftwareMicrosoftVisualStudio9.0
    • For Visual Studio 2010: SoftwareMicrosoftVisualStudio10.0
    • For Visual Studio 2012: SoftwareMicrosoftVisualStudio11.0
    • For Visual Studio 2013: SoftwareMicrosoftVisualStudio12.0
  • To detect the edition and subedition of the Visual Studio IDE you can use the IVsShell interface, calling its GetProperty method with the Microsoft.VisualStudio.Shell.Interop.__VSSPROPID2.VSSPROPID_SKUEdition and Microsoft.VisualStudio.Shell.Interop.__VSSPROPID2.VSSPROPID_SubSKUEdition values.
    Note: To get a service from an add-in, see HOWTO: Get a Visual Studio service from an add-in; and to know how to reference an assembly from the GAC (such as Microsoft.VisualStudio.Shell.Interop.dll), see HOWTO: Reference a Visual Studio assembly in the GAC from an add-in.
    The returned results are not well documented but some values are provided in the following sample add-in:
  • To detect whether a specific Visual Studio package is installed or not, you can use the IsPackageInstalled method of the IVsShell interface, which receives the Guid of the package.

Detecting installed Visual Studio Service Packs

Visual Studio uses the following Windows registry entries to track the installed service packs for the several versions (2005, 2008), editions (Standard, Professional, etc.) and languages (English, Spanish, etc.):
HKEY_LOCAL_MACHINESoftwareMicrosoftDevDivVSServicing<version><edition><localeId>

where <version> and <edition> where explained in a previous section of this article and <localeId> is 1033 for English, 3082 for Spanish, etc.

For example, when Visual Studio 2005 Team Edition for Developers has SP1 installed, the value of the 'SP' registry entry of HKEY_LOCAL_MACHINESOFTWAREMicrosoftDevDivVSServicing8.0VSTD1033 is set to 1.

To know the service at general level (without taking into account the edition and language) you can use the 'SP' registry entry under the registry key:

HKEY_LOCAL_MACHINESoftwareMicrosoftDevDivVSServicing<version>

Related articles


Go to the 'Visual Studio Extensibility (VSX)' web site for more articles like this (Articles section)

Results of browning african safari game free: Free download software, Free Video dowloads, Free Music downloads, Free Movie downloads, Games HOME BrowningAfrican Safari free download. Browning african safari deluxe free download. The Browning African Safari: Who's Hunting Who TM is the first African hunting game. The Browning African Safari. The Browning African Safari.Where Can I Download Browning African Safari A safari is an overland journey, typically a trip by tourists to Africa. African Safari Hunting Game.



View / Submit Screenshot

Visual Studio 2005, codenamed Whidbey (a reference to Whidbey Island in Puget Sound), was released online in October 2005 and to retail stores a few weeks later. Microsoft removed the '.NET' moniker from Visual Studio 2005 (as well as every other product with .NET in its name), but it still primarily targets the .NET Framework, which was upgraded to version 2.0. It is the last version available for Windows 2000 and also the last version to be able to target Windows 98, Windows Me and Windows NT 4.0 for C++ applications.

Visual Studio 2005's internal version number is 8.0 while the file format version is 9.0. Microsoft released Service Pack 1 for Visual Studio 2005 on 14 December 2006. An additional update for Service Pack 1 that offers Windows Vista compatibility was made available on 3 June 2007.

Visual Studio 2005 was upgraded to support all the new features introduced in .NET Framework 2.0, including generics and ASP.NET 2.0. The IntelliSense feature in Visual Studio was upgraded for generics and new project types were added to support ASP.NET web services. Visual Studio 2005 also includes a local web server, separate from IIS, that can host ASP.NET applications during development and testing. It also supports all SQL Server 2005 databases. Database designers were upgraded to support the ADO.NET 2.0, which is included with .NET Framework 2.0. C++ also got a similar upgrade with the addition of C++/CLI which is slated to replace the use of Managed C++. Other new features of Visual Studio 2005 include the 'Deployment Designer' which allows application designs to be validated before deployments, an improved environment for web publishing when combined with ASP.NET 2.0 and load testing to see application performance under various sorts of user loads. Starting with the 2005 edition, Visual Studio also added extensive 64-bit support. While the host development environment itself is only available as a 32-bit application, Visual C++ 2005 supports compiling for x86-64 (AMD64 and Intel 64) as well as IA-64 (Itanium). The Platform SDK included 64-bit compilers and 64-bit versions of the libraries.

Microsoft also announced Visual Studio Tools for Applications as the successor to Visual Basic for Applications (VBA) and VSA (Visual Studio for Applications). VSTA 1.0 was released to manufacturing along with Office 2007. It is included with Office 2007 and is also part of the Visual Studio 2005 SDK. VSTA consists of a customized IDE, based on the Visual Studio 2005 IDE, and a runtime that can be embedded in applications to expose its features via the .NET object model. Office 2007 applications continue to integrate with VBA, except for InfoPath 2007 which integrates with VSTA. Version 2.0 of VSTA (based on Visual Studio 2008) was released in April, 2008. It is significantly different from the first version, including features such as dynamic programming and support for WPF, WCF, WF, LINQ, and .NET 3.5 Framework.

Supported .NET Framework versions: 2.0, 3.0

The product was released 2005-11-07.