Visual Studio 2017 Platform Targeting and Compatibility

This is not the latest version of Visual Studio. To download the latest release, please visit the current release notes for Visual Studio 2019.

Visual Studio 2017 contains many new and exciting features and IDE productivity enhancements to support Windows app development, cross-platform mobile development, Azure development, web and cloud development, and more. To try out Visual Studio 2017, see Visual Studio 2017 Downloads. For more information about everything that’s new in this release, see the Visual Studio 2017 release notes and What’s New in Visual Studio 2017.

Installation

You can install and use Visual Studio 2017 alongside previous versions of Visual Studio, including Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012.

Download

Click a button to download the latest version of Visual Studio 2017. For instructions on installing and updating Visual Studio 2017, see the Update Visual Studio 2017 to the most recent release. Also, see instructions on how to install offline.

This is not the latest version of Visual Studio. To download the latest release, please visit the current release notes for Visual Studio 2019.

Visit the the Visual Studio downloads page to get the latest Visual Studio products.

Note: Installation package size will vary depending on your current Visual Studio configuration.

System Requirements

For information on the system requirements for installing and running the Visual Studio 2017 family of products, including Team Foundation Server 2017, see the Visual Studio 2017 System Requirement page and Visual Studio 2017 for Mac Product Family System Requirements.

Feedback and Support

For support, or to submit feedback on Visual Studio, see:

Upgrade Projects to Visual Studio 2017

When following the supported upgrade paths, your Visual Studio source, solutions, and project files will continue to work; however, you should expect to make some changes to sources. While we cannot guarantee binary compatibility between releases, we will do our best to document significant changes to assist you with updates.

For details on how to migrate your projects to Visual Studio 2017, see Porting, Migrating, and Upgrading Visual Studio Projects.

Platform Targeting

Visual Studio provides cutting-edge tools and technologies to create apps that take advantage of the latest platform capabilities, whether Windows, Android, iOS, or Linux. Visual Studio 2017 also targets earlier platforms so you can create new apps or modernize existing apps that execute on earlier versions of Windows while leveraging the enhanced development tools, quality enablement, and team collaboration capabilities in Visual Studio 2017. For more information, see Managing references in a project and Visual Studio Multi-Targeting Overview.

Visual Studio 2017 Support for Windows Development

The following table explains the Microsoft Windows platforms for which you can build apps by using Visual Studio 2017.

Build Apps that Run on Windows Clients	Using Tools for Native and Managed Classic Windows Desktop Development	Using Tools for UWP App Development
Windows 10	Yes (see notes below)	Yes (see notes below)
HoloLens	No	Yes See the Windows Holographic Dev Center.
Xbox One	Not applicable	Yes See the Xbox Dev Center.
Windows 8.1 (Windows 8)	Yes	Windows Store app development is not available.
Windows 7	Yes	Not applicable
Windows Vista	Yes Remote debugging and profiling tools are not available.	Not applicable
Windows XP	Yes Managed development requires using Visual Studio .NET multi-targeting. Remote debugging and profiling tools are not available.	Not applicable
Build Apps that Run on Windows Phone	Using Tools for Native and Managed Classic Windows Desktop Development	Using Tools for UWP App Development
Windows 10 Mobile	No	Yes (see notes below)
Windows Phone 8.1 and earlier	No	Windows Store app development is not available.
Build Apps that Run on Windows Server	Using Tools for Native and Managed Classic Windows Desktop Development	Using Tools for UWP App Development
Windows Server 2016	Yes	Yes (see notes below)
Windows Server 2016, Nano Server Installation Option	Yes, for .NET Core and a subset of Win32 See the Nano Server Dev Center.	No
Windows Server 2012 R2	Yes	Windows Store app development is not available.
Windows Server 2012	Yes	Windows Store app development is not available.
Windows Server 2008 R2	Yes	Not applicable
Windows Server 2008	Yes Remote debugging and profiling tools are not available.	Not applicable
Windows Server 2003	Yes Remote debugging and profiling tools are not available. Managed development requires using Visual Studio .NET multi-targeting and requires side-by-side installation of Visual Studio 2010. For more information, see: A Look Ahead at the Visual Studio 2012 Product Lineup and Platform Support.	Not applicable
Build Apps that Run on Windows Embedded Devices	Using Tools for Native and Managed Classic Windows Desktop Development	Using Tools for UWP App Development
Windows 10 IoT Core	Yes, for a subset of Win32 APIs See the IoT Core API Porting Tool for information.	Yes See the Windows IoT Dev Center for additional tools and resources.
Windows 10 IoT Mobile Enterprise	No	Yes See the Windows IoT Dev Center for additional tools and resources.
Windows 10 IoT Enterprise	Yes See the Windows IoT Dev Center for additional tools and resources.	Yes See the Windows IoT Dev Center for additional tools and resources.
Windows Embedded 8 Standard and 8.1 Industry	Yes	No
Windows Embedded Compact 2013	No	Not applicable
Windows Embedded 7 (Compact, Standard, and POSReady)	No	Not applicable
Windows Embedded CE 6.0 and earlier	No	Not applicable
Windows XP Embedded (Including POSReady 2009, WES 2009, WEPOS)	No	Not applicable

Notes

• For support information regarding Microsoft operating systems, see Microsoft Support Lifecycle and Windows 10 Release Information.
• For support information on Microsoft .NET Framework, see .NET Framework Support Lifecycle FAQ and .NET Framework System Requirements.
• Windows 10 Enterprise LTSB edition and Windows 10 S are not supported for development. You may use Visual Studio 2017 to build apps that run on Windows 10 LTSB and Windows 10 S. Remote debuging is supported on LTSB.
• Universal Windows app development for all target platforms is available when Visual Studio is installed on Windows 10.
• Universal Windows apps can be built from the command line when using Windows Server 2012 R2 or Windows Server 2016. UWP development—including designing, editing, and local debugging—is not available on Windows Server. You may deploy these apps to Windows server and debug them remotely.
• Cordova, Unity, and Xamarin can also be used for cross-platform development of Universal Windows Apps on Windows 10.

Visual Studio 2017 Support for .NET Development

Visual Studio 2017 supports development of apps that use any of the .NET implementations. Among the workloads and project types, you can find support for .NET Framework, .NET Core, Mono, and .NET Native for Universal Windows Platform (UWP). Visual Studio 2017 supports the following implementations:

For more information on each of these implementations, and on the common API specification .NET Standard, see .NET architectural components.

Visual Studio 2017 Support for Android Development

Visual Studio 2017 enables you to build native Android apps using Xamarin and C# or using Java/C++, and hybrid Android apps using Apache Cordova 6.3.1 and JavaScript and TypeScript. The Visual Studio Tools for Unity and the Unreal Engine enable Android game development. You can also use Visual Studio for Mac to build Android apps using a Mac.

You can use Visual Studio setup to easily obtain the Android SDK and Android API levels 19, 21, 22, and 23. You can download additional API levels separately using the Android SDK Manager. You can also use Visual Studio Setup to obtain the Android Native Development Kit (R10E), Java SE Development Kit, and Apache Ant.

For information on .NET development for Android, see .NET architectural components.

Visual Studio 2017 Support for iOS Development

Visual Studio 2017 enables you to build and debug apps for iOS by using Apache Cordova, C++, Unity, or Xamarin and a Mac configured for iOS development when using remotebuild, vcremote, the Visual Studio Tools for Unity, or the Xamarin Mac Agent. Xamarin supports iOS 7 and higher, and requires OS X 10.10 «Yosemite» or higher. Apache Cordova supports iOS 8 and higher, and requires OS X 10.9 «Mavericks» and higher. You can also use Visual Studio for Mac to build iOS apps using a Mac.

For more information, see Cross-platform mobile development in Visual Studio. For information on .NET development for iOS, see .NET architectural components.

Visual Studio 2017 Support for Linux Development

Visual Studio 2017 enables you to build and debug apps for Linux using C++, Python, and Node.js. Creating C++ apps for Linux requires the Visual C++ for Linux Development extension. Creating apps with Python or Node,js, requires that you enable remote debugging on the target Linux machine. You can also create, build and remote debug .NET Core and ASP.NET Core applications for Linux using modern languages such as C#, VB and F#.

For information on .NET development for Linux, see .NET architectural components.

• CentOS 7.1 and Oracle Linux 7.1
• Debian 8
• Fedora 23
• Linux Mint 17
• openSUSE 13.2
• Red Hat Enterprise Linux 7.2
• Ubuntu 14.04 and 16.04

For more information see the .NET Core Website.

Visual Studio 2017 Support for macOS Development

Visual Studio 2017 enables you to build console applications and ASP.NET applications that target macOS. However, debugging is not supported. For additional macOS development tools choices, try Visual Studio Code or Visual Studio for Mac. Visual Studio Code provides a streamlined, extensible developer tool experience for macOS. Visual Studio for Mac provides a feature-rich IDE that enables you to build native macOS apps, including ASP.NET, using C#.

For information on .NET development forMacOS, see .NET architectural components.

Other Platforms and Technologies

Visual Studio 2017 also supports the following platforms and technologies. For more information, see https://visualstudio.microsoft.com/vs/features/.

Compatibility with Previous Releases

.NET Framework

.NET 4.7 is is a highly compatible in-place update of .NET 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, and 4.6.2.

Team Explorer and Team Foundation Server

Team Explorer for Visual Studio 2017 will connect to Team Foundation Server 2017, Team Foundation Server 2015, Team Foundation Server 2013, Team Foundation Server 2012, and Team Foundation Server 2010 SP1.

Silverlight

Silverlight projects are not supported in this version of Visual Studio. To maintain Silverlight applications, continue to use Visual Studio 2015.

Windows Store and Windows Phone apps

Projects for Windows Store 8.1 and 8.0, and Windows Phone 8.1 and 8.0 are not supported in this release. To maintain these apps, continue to use Visual Studio 2015. To maintain Windows Phone 7.x projects, use Visual Studio 2012.

Alexell.Ru

Официальный сайт Alexell

Установка старых MS Visual Studio на Windows 10

Сегодня я бы хотел затронуть процесс установки старых версий Microsoft Visual Studio на Windows 10. Пригодится тем, кто уже успел пересесть на «десятку» или купил ПК/ноутбук, где она была предустановлена. Если не хотите читать всю историю и ищете готовое решение проблемы — просто прокрутите страницу в самый низ, рабочее решение там.

Зачем устанавливать старую версию, спросите вы? Отвечу так: у каждого проекта свои задачи, потребности, идеи, и проблемы, для решения которых может потребоваться установка именно версии 2013 года, например. В работе над обновлением Celestia мне помогает один иностранец. Он до сих пор пользуется Windows XP и позволил себе апгрейд только до MS Visual Studio 2013. Поэтому и мне пришлось эту версию, поскольку в 2017-й его проекты не компилируются (уж больно тонко он заточил их именно под 2013).

Я скачал замечательную раздачу MS Visual Studio 2013 Ultimate и, не ожидая никаких подводных камней, монтировал ISO образ, запустил установку и . обломался. Установщик выдал сообщение с заголовном «Setup Blocked» и текстом «Windows Program Compatibility mode is on. Turn it off and then try Setup again» (скриншот в начале поста). Я человек разбирающийся, поэтому сразу полез в процессы и службы, чтобы найти что либо похожее. В итоге в службах я нашел «Служба помощника по совместимости программ».

Я остановил его в службах (Диспетчер задач), а в компоненте «Службы» вообще полностью отключил. Перезагрузив ПК, я понял что установщик MS Visual Studio 2013 все равно выдает ту же ошибку. После поиска на англоязычных ресурсах, я узнал несколько любопытных вещей, например, что Windows Program Compatibility проверяет по стандартным (оригинальным) именам пакетов установки Microsoft и для решения проблемы достаточно переименовать файл установщика, например дописав ему суффикс «(1)». После распаковки ISO в папку, пришлось искать дальше, потому что это тоже не помогло.