Port, Migrate, and Upgrade Visual Studio Projects
Each new version of Visual Studio generally supports most previous types of projects, files, and other assets. You can work with them as you always have, and provided that you don't depend on newer features, Visual Studio preserves backwards compatibility with previous versions like Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012. (See the Release Notes for which features are specific to which versions.)
Support for some types change over time, however. A newer version of Visual Studio may no longer support certain types, or require that they be migrated and updated such that they're no longer backwards-compatible. For current status on migration issues, refer to the Visual Studio Developer Community site.
This present topic provides details only for project types in Visual Studio 2017 that involve migration. It does not include supported project types that have no migration issues; that list is found on found in the Platform Targeting and Compatibility. Note also that some project types are no longer supported at all in Visual Studio 2017 and therefore cannot be migrated.
Adding appropriate workloads in the Visual Studio installer is necessary for opening certain project types. If you don't have the workload installed, Visual Studio will report an unknown or incompatible project type. In that case, check your installation options and try again. Again, see the Platform Targeting and Compatibility topic for details on project support in Visual Studio 2017.
The following list describes support in Visual Studio 2017 for projects that were created in earlier versions.
If you don't see a project or file type listed here that should be, please consult the Visual Studio 2015 version of this topic and make a note in the comments below.
|Type of Project||Support|
|.NET Core projects (.xproj)||Projects created with Visual Studio 2015 used preview tooling which include a .xproj project file. When you open a .xproj file with Visual Studio 2017, you will be prompted to migrate the file to the .csproj format (a backup of the .xproj file is made). This .csproj format for .NET Core projects is not supported in VS2015 and earlier. The .xproj format is not supported in Visual Studio 2017 other than for migration to .csproj. For more information, see Migrating .NET Core projects to the .csproj format.|
|ASP.NET Web Application and ASP.NET Core Web Application with Application Insights enabled||For each Visual Studio user, resource information is stored in the registry per user instance. This is used when user don't have a project opened and wants to search Azure Application Insights data. Visual Studio 2015 uses different registry location than Visual Studio 2017 and does not conflict.
Once a user creates an ASP.NET Web Application or ASP.NET Core Web Application, the resource is stored in the .suo file. The user can open the project in Visual Studio 2015 or 2017 and the resource information will be used for both as long as Visual Studio supports projects and solutions being used across both versions. Users will need to authenticate once on each product. For example, if a project is created with Visual Studio 2015 and opened in Visual Studio 2017, the user will need to authenticate on Visual Studio 2017.
|C#/Visual Basic Webform or Windows Form||You can open the project in Visual Studio 2017 and Visual Studio 2015.|
|Database Unit Test Projects (.csproj, .vbproj)||Older Data Unit test projects will be loaded in Visual Studio 2017 but will use the GAC’d version of dependencies. To upgrade the unit test project to use the latest dependencies right click on the project in Solution Explorer and select Convert to SQL Server Unit Testing Project....|
|F#||Visual Studio 2017 can open projects created in Visual Studio 2013 and 2015. To enable Visual Studio 2017 features in these projects, however, open the project properties and change target fsharp.core to F# 4.1. Note also that the F# language support option in the Visual Studio installer is not selected by default with .NET workloads; you must include it by selecting that option for the workload, or selecting it from the Individual components tab under Development activities.|
|Installer projects created in Visual Studio 2010 can be opened in later versions with the help of the Visual Studio Installer Projects extension. Also see the WiX Toolset Visual Studio 2017 Extension. InstallShield Limited Edition is no longer included with Visual Studio. Check with Flexera Software about availability for Visual Studio 2017.|
|LightSwitch||LightSwitch is no longer supported in Visual Studio 2017. Projects created with Visual Studio 2012 and earlier opened in Visual Studio 2013 or Visual Studio 2015 will be upgraded and can be opened only in Visual Studio 2013 or Visual Studio 2015 thereafter.|
|Microsoft Azure Tools for Visual Studio||To open these types of projects, first install the Azure SDK for .NET, then open the project. If necessary, your project will be updated.|
|Model-View-Controller framework (ASP.NET MVC)||Support for MVC versions and Visual Studio:
Upgrading MVC versions:
|Modeling||If you allow Visual Studio to update the project automatically, you can open it in Visual Studio 2015, Visual Studio 2013, or Visual Studio 2012.
The format of the modeling project has not changed between Visual Studio 2015 and Visual Studio 2017 and the project can be opened and modified in either version. However, there are differences in behavior in Visual Studio 2017:
|MSI Setup (.vdproj)||See InstallShield Projects above.|
|Office 2007 VSTO||Requires a one-way upgrade for Visual Studio 2017.|
|Office 2010 VSTO||If the project targets the .NET Framework 4, you can open it in Visual Studio 2010 SP1 and later. All other projects require a one-way upgrade.|
|SharePoint 2010||When a SharePoint solution project is opened with Visual Studio 2017, it will be upgraded to either SharePoint 2013 or SharePoint 2016. The ".NET Desktop Development" workload must be installed in Visual Studio 2017 for the upgrade.
For more information about how to upgrade SharePoint projects, see Upgrade to SharePoint 2013, Update Workflow in SharePoint Server 2013, and Create the SharePoint Server 2016 farm for a database attach upgrade.
|SharePoint 2016||SharePoint Add-In projects created in Office Developer Tools Preview 2 cannot be opened in Visual Studio 2017. To work around this you will need to update the
|Silverlight||Silverlight projects not supported in Visual Studio 2017. To maintain Silverlight applications, continue to use Visual Studio 2015.|
|SQL Server Reporting Services and SQL Server Analysis Services (SSRS, SSDT, SSAS, MSAS)||Support for these project types is provided through two extensions in the Visual Studio Gallery: Microsoft Analysis Services Modeling Projects and Microsoft Reporting Services Projects. SSDT support is also included with the Data Storage and Processing workload in Visual Studio 2017.|
|SQL Server Integration Services (SSIS)||Support is not yet available for Visual Studio 2017. It will be announced on the SQL Server Integration Services blog. The present recommendation for SSIS is to continue using Visual Studio 2015.|
|Visual C++||You can use Visual Studio 2017 to open solutions and projects that were created in Visual Studio 2015 as-is, but projects that were created in older versions of Visual Studio may require upgrading the project or retargeting to a more recent toolset to build with Visual Studio 2017. For more information, see Visual C++ Porting and Upgrading Guide.|
|Visual Studio Extensibility/VSIX||Projects with MinimumVersion 14.0 or less will be updated to declare MinimumVersion 15.0, which prevents the project from being opened in earlier versions of Visual Studio. To allow a project to open in earlier versions, set MinimumVersion to
|Visual Studio Lab Management||You can use Microsoft Test Manager or Visual Studio 2010 SP1 and later to open environments created in any of these versions. However, for Visual Studio 2010 SP1 the version of Microsoft Test Manager must match the version of Team Foundation Server before you can create environments.|
|Visual Studio Tools for Apache Cordova||This project can be opened in Visual Studio 2017, but it is not backwards compatible. Upon opening a project from Visual Studio 2015, you will be prompted to allow modifications to your project. This upgrades the project to use toolsets instead of a
|Windows Communication Foundation, Windows Workflow Foundation||You can open this project in Visual Studio 2017, Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012|
|Windows Presentation Foundation||You can open this project in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1.|
|Windows Store/Phone apps||Projects for Windows Store 8.1 and 8.0, and Windows Phone 8.1 and 8.0 are not supported in Visual Studio 2017. To maintain these apps, continue to use Visual Studio 2015. To maintain Windows Phone 7.x projects, use Visual Studio 2012.|