Windows 7 visual studio 2017

Visual Studio 2017 – Now Ready for Your Windows Application Development Needs

Visual Studio 2017 is the most powerful Universal Windows Platform development environment. It brings unparalleled productivity improvements, a streamlined acquisition experience and enhanced debugging tools for Universal Windows Platform developers.

Try out Visual Studio 2017 today!

Redefined fundamentals

We have focused on enhancing the efficiency of basic tasks you encounter every day, starting with a brand-new lightweight and modular installer, a faster and more responsive IDE from start-up to shut down and a new way to view, edit and debug any code without projects and solutions.

Brand-new lightweight and modular installation tailored to your needs – The new lightweight and componentized installer breaks Visual Studio down into independent workloads so you can install just what you need, helping you get to coding much faster. The Universal Windows Platform development workload gives you the right tools to be productive in authoring, debugging and publishing UWP apps. If something is missing, you will be able to add it later using the Visual Studio Installer.

Faster startup and shorter solution load time –  Visual Studio is three times faster for a cold start and two to three times faster for solution loading. This has been made possible by moving extensions out of the startup path using an on-demand-load approach and optimizing and deferring cache initializations. For example, the first launch startup times have improved from 206 seconds in VS 2015 to 64.2 seconds in VS 2017.

Boosted Productivity

In Visual Studio 2017, we have made improvements to code navigation, IntelliSense, refactoring, code fixes and debugging to save you time and effort on everyday tasks irrespective of language or platform.

IntelliSense – You can now blaze through authoring your XAML with the new IntelliSense completion for x:Bind and namespace completion.

IntelliSense has been enhanced with improved filtering that makes long lists much more manageable. IntelliSense is also smarter with CamelCase search and the ability to select the best matching result from the list instead of simply picking the top result.

Code refactoring – Visual Studio 2017 expands the set of refactorings and fixes to help you maintain a readable code base and accelerate your development workflows. For example, you can de-clutter your XAML using the “Remove Unnecessary Namespaces” quick fix and retain only those you need. If you end up removing a namespace that you need later, the “add missing namespace” quick fix helps you add it back.

Navigation – Navigate To is much more powerful with better filtering and preview. We have also enhanced Find All Reference by adding color, grouping and a peek preview in the Find All References window.

Run to Click – Run to Click does exactly what it sounds like; it executes a program until it reaches the targeted line of code and breaks in debug mode. Essentially, it removes the need for developers to constantly add, hit and remove temporary breakpoints by combining all these actions into one click.

Streamlined Azure Development

Visual Studio 2017 comes with a suite of Connected Services that enables you to easily create engaging cloud-first applications powered by Microsoft Azure. Directly from the IDE, you can configure and connect to an Azure Mobile App Service to enable cloud storage, push notifications, authentication and social integration. You can also connect to HockeyApp for app analytics, beta distribution, in-app feedback and track customer metrics.

Five star UWP app development

Discover accessibility and performance issues with the new UI Analysis tool – The UI Analysis tool examines the elements in your app and helps you quickly discover hard-to-find issues around accessibility and UI performance. Additionally, it points to exactly what needs to be done to fix these issues, resulting in high performant five-star apps.

Edit XAML for a running app with runtime editing tools – XAML Edit and Continue lets you change your XAML while the app is running and get immediate feedback. On its own, Edit and Continue is amazingly powerful. When combined with the UI Debugging tools, developers can fix problems faster than ever before and create performant, adaptive and stunning UI.

Auto-generate visual assets for your UWP apps – The brand new manifest asset generator enables you to create all the visual assets for your app from within the Manifest Designer. Using a single source image, you can now create tiles, logos, icons and splash screens at any or all scales to fit every type of device your app targets. We take care of adhering to all the design guidelines suggested for Windows 10 apps like padding and background colors.

Build awesome apps with the Windows 10 Creators Update – Visual Studio 2017 is the first release to support building Universal Windows Platform apps for the Windows 10 Creators Update. We’ve made strides to improve the SDK acquisition, so you only get what you need. This should help you get started as quickly as possible. The Creators Update brings many changes to the platform which you can read about here.

Ready, Set, Build!

If you haven’t already, get started with building your first Universal Windows app with Visual Studio 2017. As always, we welcome your feedback. If you find an issue, let us know via the Report a Problem option in the upper right corner, either from the installer or the Visual Studio IDE itself. Track your feedback on the developer community portal. For suggestions, let us know through UserVoice.

Updated March 7, 2017 10:01 am

Необходимые компоненты для .NET Core в Windows

В этой статье описываются зависимости, необходимые для разработки приложений .NET Core в Windows. Поддерживаемые версии ОС, а также перечисленные ниже зависимости относятся к трем способам разработки приложений .NET Core в Windows:

Версии Windows, поддерживаемые .NET Core

Платформа .NET Core поддерживается в следующих версиях:

  • Windows 7 SP1
  • Windows 8.1
  • Windows 10, юбилейное обновление Windows 10 (версия 1607) или более поздние версии
  • Windows Server 2008 R2 с пакетом обновления 1 (SP1) (полный сервер или основные серверные компоненты)
  • Windows Server 2012 с пакетом обновления 1 (SP1) (полный сервер или основные серверные компоненты)
  • Windows Server 2012 R2 (полный сервер или основные серверные компоненты)
  • Windows Server 2016 (полный сервер, основные серверные компоненты или сервер Nano)

Полный список операционных систем, поддерживаемых .NET Core 2.x, см. в статье Версии ОС, поддерживаемые .NET Core 2.x.

Полный список операционных систем, поддерживаемых .NET Core 1.x, см. в статье Версии ОС, поддерживаемые .NET Core 1.x.

Зависимости .NET Core

Для запуска платформы .NET Core в версиях до Windows 10 и Windows Server 2016 необходим распространяемый компонент Visual C++. Эта зависимость устанавливается автоматически установщиком .NET Core.

Распространяемый компонент Microsoft Visual C++ 2015 с обновлением 3 необходимо установить вручную в следующих случаях:


Только для компьютеров под управлением Windows 7 и Windows Server 2008.Убедитесь, что установка Windows актуальна, а исправление KB2533623 установлено через Центр обновления Windows.

Необходимые компоненты для Visual Studio 2017

Для разработки приложений .NET Core с помощью пакета SDK для .NET Core вы можете использовать любой редактор. Visual Studio 2017 предоставляет интегрированную среду разработки для приложений .NET Core в Windows.

Дополнительные сведения об обновлениях Visual Studio 2017 см. в заметках о выпуске.

Для разработки приложений .NET Core 2.x в Visual Studio 2017 выполните указанные ниже действия.

  1. Скачайте и установите Visual Studio 2017 версии 15.3.0 или более поздней с выбранной рабочей нагрузкой Кроссплатформенная разработка .NET Core (в разделе Другие наборы инструментов).

После установки набора инструментов Кроссплатформенная разработка .NET Core среда Visual Studio 2017 по умолчанию использует .NET Core 1.x. Чтобы в среде Visual Studio 2017 поддерживалась платформа .NET Core 2.x, установите пакет SDK для .NET Core 2.x.

  1. Установите пакет SDK для .NET Core 2.x.
  2. Перенацельте существующие или новые проекты .NET Core 1.x на .NET Core 2.x, выполнив приведенные ниже инструкции.
    • В меню Проект выберите пункт Свойства.
    • В меню Целевая платформа выберите значение .NET Core 2.0.

После установки пакета SDK для .NET Core 2.x среда Visual Studio 2017 по умолчанию использует пакет SDK для .NET Core 2.x и поддерживает следующие действия:

  • открытие, сборка и запуск существующих проектов .NET Core 1.x;
  • перенацеливание проектов .NET Core 1.x на .NET Core 2.x, сборка и запуск;
  • создание проектов .NET Core 2.x.

Для разработки приложений .NET Core 1.x в Visual Studio скачайте и установите Visual Studio 2017 RTM (версия 15.0.26228.4) или более позднюю версию с выбранной рабочей нагрузкой Кроссплатформенная разработка .NET Core (в разделе Другие наборы инструментов).


Для разработки приложений .NET Core 1.x можно использовать среду Visual Studio 2015, но делать этого не рекомендуется по указанным ниже причинам.

  • Средства .NET Core доступны в виде предварительной версии, которая не поддерживается.
  • Проекты основаны на файлах project.json, которые являются нерекомендуемыми.

Дополнительные сведения об изменениях формата проектов см. в этом обзоре.


Чтобы проверить установленную версию Visual Studio 2017, выполните указанные ниже действия.

  • В меню Справка выберите пункт О программе Microsoft Visual Studio.
  • В диалоговом окне О программе Microsoft Visual Studio проверьте номер версии.
    • Для приложений .NET Core 2.x требуется среда Visual Studio 2017 версии 15.3 (26730.01) или более поздней.
    • Для приложений .NET Core 1.x требуется среда Visual Studio 2017 версии 15.0 (26228.04) или более поздней.

Prerequisites for .NET Core on Windows

This article shows the dependencies needed to develop .NET Core applications on Windows. The supported OS versions and dependencies that follow apply to the three ways of developing .NET Core apps on Windows:

.NET Core supported Windows versions

.NET Core is supported on the following versions of :

  • Windows 7 SP1
  • Windows 8.1
  • Windows 10, Windows 10 Anniversary Update (version 1607) or later versions
  • Windows Server 2008 R2 SP1 (Full Server or Server Core)
  • Windows Server 2012 SP1 (Full Server or Server Core)
  • Windows Server 2012 R2 (Full Server or Server Core)
  • Windows Server 2016 (Full Server, Server Core, or Nano Server)

See .NET Core 2.x - Supported OS Versions for the complete list of .NET Core 2.x supported operating systems.

See .NET Core 1.x Supported OS Versions for the complete list of .NET Core 1.x supported operating systems.

.NET Core dependencies

.NET Core 1.1 and earlier requires the Visual C++ Redistributable when running on Windows versions earlier than Windows 10 and Windows Server 2016. This dependency is automatically installed by the .NET Core installer.

Microsoft Visual C++ 2015 Redistributable Update 3 must be manually installed when:

  • Installing .NET Core with the installer script.
  • Deploying a self-contained .NET Core application.


For Windows 7 and Windows Server 2008 machines only:Make sure that your Windows installation is up-to-date and includes hotfix KB2533623 installed through Windows Update.

Prerequisites with Visual Studio 2017

You can use any editor to develop .NET Core applications using the .NET Core SDK. Visual Studio 2017 provides an integrated development environment for .NET Core apps on Windows.

You can read more about the changes in Visual Studio 2017 in the release notes.

To develop .NET Core 2.x apps in Visual Studio 2017:

  1. Download and install Visual Studio 2017 version 15.3.0 or higher with the .NET Core cross-platform development workload (in the Other Toolsets section) selected.

After the .NET Core cross-platform development toolset is installed, Visual Studio 2017 uses .NET Core 1.x by default. Install the .NET Core 2.x SDK to get .NET Core 2.x support in Visual Studio 2017.

  1. Install the .NET Core 2.x SDK.
  2. Retarget existing or new .NET Core 1.x projects to .NET Core 2.x using the following instructions:
    • On the Project menu, Choose Properties.
    • In the Target framework selection menu, set the value to .NET Core 2.0.

Once the .NET Core 2.x SDK is installed, Visual Studio 2017 uses the .NET Core SDK 2.x by default, and supports the following actions:

  • Open, build, and run existing .NET Core 1.x projects.
  • Retarget .NET Core 1.x projects to .NET Core 2.x, build, and run.
  • Create new .NET Core 2.x projects.

To develop .NET Core 1.x apps in Visual Studio, download and install Visual Studio 2017 RTM (version 15.0.26228.4) or higher with the ".NET Core cross-platform development" workload (in the Other Toolsets section) selected.


It's possible to use Visual Studio 2015 for .NET Core 1.x development, but it's not recommended for the following reasons:

  • The .NET Core tooling is a preview version, which is not supported.
  • The projects are project.json-based, which is deprecated.

For more information about the project format changes, see High-level overview of changes.


To verify your Visual Studio 2017 version:

  • On the Help menu, choose About Microsoft Visual Studio.
  • In the About Microsoft Visual Studio dialog, verify the version number.
    • For .NET Core 2.x apps, Visual Studio 2017 version 15.3 (26730.01) or higher.
    • For .NET Core 1.x apps, Visual Studio 2017 version 15.0 (26228.04) or higher.

Visual Studio 2017: Productivity, Performance, and Partners

Today we released Visual Studio 2017. Start your download and read on to learn more about some of the highlights of this release. For the complete list of changes in the release, check out the Visual Studio 2017 release notes. Some of the things I would like to highlight are:

Fundamentals: Productivity and Performance

Improved startup and improved project load. Multiple enhancements come together to make Visual Studio 2017 start up faster than Visual Studio 2015. Solution load times are shorter, and build performance is faster, particularly for C++ projects as Ankit Asthana wrote on the VC++ blog. Check out this post by Dan Taylor on improved overall Visual Studio responsiveness that leads you into a deep dive on these improvements.

Enhanced Navigation. Visual Studio 2017 dramatically improves code navigation, from “Go to All” to Find All References to Indent Guides. For example, Find All References used to display its search results as a flat list in the Results Window. Visual Studio 2017 colorizes the results and provides custom grouping, sorting, filtering, and searching to help you rapidly home in on the specific reference you were looking for. But most powerful is Go to All (ctrl+T or ctrl+,), which has undergone a complete transformation. Go to All is a fast, complete search for any file, type, member or symbol declaration in a solution. Icons at the bottom of the search bar allow you to filter your results by group or adjust the scope of the search. You can also customize settings like placement of the search bar, a live preview of the files containing the highlighted result, and additional file information for each result, by clicking the gear icon in the bottom-right corner.

Keyboard Shortcuts for GoTo

Go To All Go To Line Go To File Go To Type Go To Member Go To Symbol
Shortcut Ctrl+T or Ctrl+, Ctrl+G Ctrl+1, F Ctrl+1, T Ctrl+1, M Ctrl+1, S
Query Prefix No prefix : f t m #

Load files without needing a solution. One request we heard from customers was to be able to edit files without needing to open a project or solution. We listened and are happy to bring you a solution (wordplay mildly intended): in Visual Studio 2017, you can open and work on any file for a long list of languages from C# to C++ to Ruby to Go. For a full list of all capabilities available to you read this blog post on open any folder in Visual Studio.

IntelliSense filtering. IntelliSense now provides filters to quickly narrow down that member you’ve been looking for. Filtering helps you get to what you need without having to wade through many, many types to get to it.

Language improvements: refactorings, style analyzers, and more. There’s more here than we can easily fit into a short paragraph. We’ve added new C# language refactoring commands that help you modernize your code to the latest standard. New style analyzers and support for EditorConfig let you harmonize coding standards across your team. You can edit XAML while your WPF or UWP application is running and see changes in real-time. The C++ compiler and standard library are updated to enhance support for C++11 and C++14 features. Lastly, a new language service for TypeScript and JavaScript, provides support for the latest standard JavaScript features and provides rich type inference across both languages.

CMake support for C++. Support for CMake is now available in Visual Studio 2017. You can start coding by directly loading your CMake projects in Visual Studio. It is easy to switch between configurations provided by CMake and CppProperties.json file. Further configuration is also supported via CMakeSettings.json file that sits in the same folder as CMakeLists.txt file. For an overview of CMake support see the Visual C++ Team blog or watch this 10-minute CMake Video.

Linux support for C++. Visual C++ for Linux Development is a popular extension which is now part of Visual Studio 2017. To learn more about Linux development with C++ watch this video.

Live unit testing. Live unit testing, as the name suggests, tells you in real time if your unit tests will pass or fail because of the edits you just made to your code, without leaving the code editorin. Check out this blog post to learn more about live unit testing in Visual Studio 2017.

Run to Click. Most of us use temporary breakpoints. Run to Click is much slicker. Now while you’re stopped at a break state under the debugger, when you hover your mouse over a line of code you’ll see the Run to Click glyph. Click on the glyph and execution continues to and halts on that line.

Exception Helpers. We’ve added exception helpers, so you can immediately see the root cause of an exception with instant access to inner exceptions in a compact, non-modal dialog. Additionally, you can now exclude breaking on exception types thrown from specific modules by clicking the checkbox to add a condition while stopped at the thrown exception.

Small and lightweight installation. We made it easier to get up and running with Visual Studio 2017 with our new installer. The smallest installation is just one-tenth of the size of the previous version, and it installs in just a minute or two. We make it easy for you to install just the frameworks and tools you need to get up and running quickly.

5-Star Mobile Applications

Xamarin Forms Previewer. One of the most time-consuming parts of development is the build and run cycle – the time between writing a line of code and seeing it execute. Real-time feedback makes development faster, easier, and more fun for developers. The Xamarin Forms Previewer renders a live preview of a page side-by-side with the XAML markup, allowing you to see your user interface come to life in Visual Studio as you type.

Improved Xamarin Forms XAML IntelliSense. When you open any XAML document for Xamarin Forms in Visual Studio 2017, you will now greatly improved IntelliSense. The new IntelliSense supports bindings, custom properties, custom controls, converters, and much more.

Connected Services. The new Connected Services experience in Visual Studio 2017 makes it much easier to connect your mobile application to cloud services such as Azure Mobile Apps data storage and authentication . Adding a service to your project will add all required dependencies and any required initialization code to your mobile targets.

The first Connected Service we are providing for mobile developers enables you to connect your app to an Azure App Service backend, providing easy access to authentication, push notifications, and data storage with online/offline sync. This feature also allows you to create a new App Service directly from Visual Studio and have it provisioned without having to visit the Azure Portal.

Cloud Development

.NET Core. Visual Studio 2017 now supports building .NET Core 1.0 and 1.1 applications. .NET Core, which includes ASP.NET Core and Entity Framework Core, is Microsoft’s open source framework for building cloud and server applications and microservices for Windows, macOS, and Linux. It is fast and lightweight: on the Tech Empower web benchmark ASP.NET Core scores in the top 10 fastest web frameworks ahead of Java servlets, Node, Ruby, and PHP.

Simplified container support. Container development automates the repetitive tasks of setting up and configuring development environments. No longer do developers have to install complex software on their machines in order to duplicate their production machines, instead relying on a simple file that pulls in dependencies as a packaged container. Visual Studio 2017 supports building containerized applications on both Windows and Linux. .NET Core and .NET applications can be containerized during creation or after creation with a simple right-click gesture and can be run and debugged inside the container during local development.

Azure App Service support. Azure App Service provides hosting on ASP.NET and ASP.NET Core and Visual Studio has great support for publishing and debugging applications on App Service. Visual Studio 2017 now expands that support to hosting .NET Core containerized applications in App Service. .NET and Visual Studio 2017 make container development easy.

For additional details check out the latest posts on .NET Blog.


Visual Studio 2017 improves many aspects of working in DevOps environments, from improvements to version control to improvements to the Developer Analytics tools to a preview of the ability to configure a CI/CD pipeline directly from within Visual Studio. Of particular interest are some of the improvements in Visual Studio’s Git support. We’ve added new Git features to Visual Studio that allow you to do more of your end-to-end workflow without leaving the IDE. You can easily view the diff for outgoing commits, perform a force push to complete a rebase or push an amended commit, remove your upstream branch, and continue patch rebase from Visual Studio. Additionally, because we moved to git.exe–which allows us to provide the most up-to-date features–we support SSH, respect your config options, and show in Team Explorer exactly what you see in the command line.

Most interestingly Visual Studio also includes tools not just to perform DevOps on your source code, but on your database configuration as well, thanks to the inclusion of the Redgate Developer Tools Core Edition. To extend Visual Studio 2017 DevOps capabilities to SQL Server database development, install the Data Storage and Processing workload and you’ll get:

  • Redgate SQL Search. Redgate SQl Search is included with all editions of Visual Studio 2017, increases your productivity by helping you quickly find SQL fragments and objects across multiple databases.
  • Redgate ReadyRoll Core. Redgate ReadyRoll Core is included with Visual Studio Enterprise 2017, helps you develop migration scripts, manage database changes using source control, and safely automate deployments of SQL Server database changes alongside applications changes.
  • Redgate SQL Prompt Core. Redgate SQL Prompt Core is included with Visual Studio Enterprise 2017, helps you write, format, and refactor SQL code. You can write SQL more quickly and accurately with the help of intelligent code completion. SQL Prompt autocompletes database and system objects and keywords, and offers column suggestions as you type. This results in cleaner code and fewer errors because you don’t need to remember every column name or alias.

Additionally, your Visual Studio Enterprise subscription comes with six months of access to WhiteSource Bolt for open source vulnerability management and license checking, and to Parasoft for service virtualization. Check out the new subscriber benefits post for more details.

The Visual Studio Ecosystem

Many customers extend Visual Studio with solutions from the Visual Studio Marketplace. With today’s announcement, we have over 100 partners simultaneously shipping their extensions with the release, making over 700 extensions available to use with Visual Studio 2017.

One of the more popular extensions is Microsoft’s Productivity Power Tools. Over the last year, we’ve been reconfiguring the Power Tools to be a discrete set of extensions, and today we’re making many of them available in Visual Studio 2017.


Also, today we’re making available a preview of the Python Tools. We wanted to ensure that you have access to the Python tooling, as we are finishing up the full localization to enable us to publish them in a future minor update to all interested Visual Studio 2017 users.

Try it out and please give feedback

By now, Visual Studio 2017 may have finished installing for you. If it has, great! I’d like to address two questions we get asked a lot:

  • Can I install Visual Studio 2017 alongside Visual Studio 2015? Yes. Visual Studio 2017 works side by side with these previous versions of Visual Studio: Visual Studio 2012, Visual Studio 2013, and Visual Studio 2015. Visual Studio 2017 can’t run side by side with an RC or preview version of Visual Studio 2017 or Visual Studio “15”.
  • Can I install Visual Studio 2017 on top of a Visual Studio “15” Preview or Visual Studio 2017 RC? If you currently have Visual Studio 2017 RC or Visual Studio “15” Preview installed on your machine, you should see an ‘update’ button in the new installer. Click that and you will be good to go.

If you’re looking for the data science workload that was in VS 2015, it will be coming in a future update including R support.

If you have further questions, read the Visual Studio 2017 FAQ for other commonly asked questions. Want to know more about compatibility, check out Visual Studio 2017 compatibility and Visual Studio 2017 system requirements. Also, be sure to read this article to learn about offline installations.

Visual Studio 2017 has a lot of new and improved features for you to try. For the complete list of what is included in this release, along with some known issues, check out the Visual Studio 2017 Release Notes.

As always, we welcome your feedback. For problems, let us know via the Report a Problem option in the upper right corner, either from the installer or the Visual Studio IDE itself. Track your feedback on the developer community portal. For suggestions, let us know through UserVoice.

Finally, check out Visual Studio 2017 Launch Event to see members of the engineering team demo the product, and tune in on March 8 for a full day of live training.

John Montgomery, Director of Program Management, Visual [email protected]

John is responsible for product design and customer success for all of Visual Studio, C++, C#, VB, JavaScript, and .NET. John has been at Microsoft for 18 years, working in developer technologies the whole time.

Install certificates needed for Visual Studio offline installation

Visual Studio is primarily designed to be installed on an internet-connected machine, since many components are updated regularly. However, with some extra steps, it's possible to deploy Visual Studio in an environment where a working internet connection is unavailable.

The Visual Studio setup engine installs only content that is trusted. It does this by checking Authenticode signatures of the content being downloaded and verifying that all content is trusted before installing it. This keeps your environment safe from attacks where the download location is compromised. Visual Studio setup therefore requires that several standard Microsoft root and intermediate certificates are installed and up-to- date on a user's machine. If the machine has been kept up to date with Windows Update, signing certificates usually are up to date. If the machine is connected to the internet, during installation Visual Studio may refresh certificates as necessary to verify file signatures. If the machine is offline, the certificates must be refreshed another way.

How to refresh certificates when offline

There are three options for installing or updating certificates in an offline environment.

Option 1 - Manually install certificates from a layout folder

When you create a network layout, the necessary certificates are downloaded to the Certificates folder. You can then manually install the certificates by double-clicking each of the certificate files, and then clicking through the Certificate Manager wizard. If asked for a password, leave it blank.

Option 2 - Distribute trusted root certificates in an enterprise environment

For enterprises with offline machines that do not have the latest root certificates, an administrator can use the instructions on the Configure Trusted Roots and Disallowed Certificates page to update them.

Option 3 - Install certificates as part of a scripted deployment of Visual Studio

If you are scripting the deployment of Visual Studio in an offline environment to client workstations, you should follow these steps:

  1. Copy the Certificate Manager Tool (certmgr.exe) to the installation share (for example, \server\share\vs2017). Certmgr.exe is not included as part of Windows itself, but is available as part of the Windows SDK.

  2. Create a batch file with the following commands:

    certmgr.exe -add -c certificates\manifestSignCertificates.p12 -n "Microsoft Code Signing PCA 2011" -s -r LocalMachine CA certmgr.exe -add -c certificates\manifestSignCertificates.p12 -n "Microsoft Root Certificate Authority" -s -r LocalMachine root certmgr.exe -add -c certificates\manifestCounterSignCertificates.p12 -n "Microsoft Time-Stamp PCA 2010" -s -r LocalMachine CA certmgr.exe -add -c certificates\manifestCounterSignCertificates.p12 -n "Microsoft Root Certificate Authority" -s -r LocalMachine root certmgr.exe -add -c certificates\vs_installer_opc.SignCertificates.p12 -n "Microsoft Code Signing PCA" -s -r LocalMachine CA certmgr.exe -add -c certificates\vs_installer_opc.SignCertificates.p12 -n "Microsoft Root Certificate Authority" -s -r LocalMachine root
  3. Deploy the batch file to the client. This command should be run from an elevated process.

What are the certificates files in the Certificates folder?

The three .P12 files in this folder each contain an intermediate certificate and a root certificate. Most systems that are current with Windows Update have these certificates already installed.

  • ManifestSignCertificates.p12 contains:
    • Intermediate certificate: Microsoft Code Signing PCA 2011
      • Not required. Improves performance in some scenarios if present.
    • Root certificate: Microsoft Root Certificate Authority 2011
      • Required on Windows 7 Service Pack 1 systems that do not have the latest Windows Updates installed.
  • ManifestCounterSignCertificates.p12 contains:
    • Intermediate certificate: Microsoft Time-Stamp PCA 2010
      • Not required. Improves performance in some scenarios if present.
    • Root certificate: Microsoft Root Certificate Authority 2010
      • Required for Windows 7 Service Pack 1 systems that do not have the latest Windows Updates installed.
  • Vs_installer_opc.SignCertificates.p12 contains:
    • Intermediate certificate: Microsoft Code Signing PCA
      • Required for all systems. Note that systems with all updates applied from Windows Update might not have this certificate.
    • Root certificate: Microsoft Root Certificate Authority
      • Required. This certificate ships with systems running Windows 7 or later.

Why are the certificates from the Certificates folder not installed automatically?

When a signature is verified in an online environment, Windows APIs are used to download and add the certificates to the system. Verification that the certificate is trusted and allowed via administrative settings occurs during this process. This verification process cannot occur in most offline environments. Installing the certificates manually allows enterprise administrators to ensure the certificates are trusted and meet the security policy of their organization.

Checking if certificates are already installed

One way to check on the installing system is to follow these steps:

  1. Run mmc.exe.a. Click File, and then select Add/Remove Snap-in.b. Double-click Certificates, select Computer account, and then click Next.c. Select Local computer, click Finish, and then click OK.d. Expand Certificates (Local Computer).e. Expand Trusted Root Certification Authorities, and then select Certificates.

    • Check this list for the necessary root certificates.

    f. Expand Intermediate Certification Authorities, and then select Certificates.

    • Check this list for the required intermediate certificates.
  2. Click File and select Add/Remove Snap-in.a. Double-click Certificates, select My user account, click Finish, and then click OK.b. Expand Certificates – Current User.c. Expand Intermediate Certification Authorities, and then select Certificates.

    • Check this list for the required intermediate certificates.

If the certificates names were not in the Issued To columns, they must be installed. If an intermediate certificate was only in the Current User Intermediate Certificate store, then it is available only to the user that is logged in. You might need to install it for other users.

Install Visual Studio

After you install the certificates, deployment of Visual Studio can proceed by using the instructions from the Deploying from a network installation section of the "Create a network installation of Visual Studio" page.

See also

Смотрите также