When upgrading from Microsoft Visual Studio 2012 to Visual Studio 2013 you will take advantage of a refreshed and simplified environment with enhanced performance without any additional hardware requirements. Some of these core enhancements make use of capabilities that are only present in the latest versions of Windows and might require you to upgrade to a supported operating system.
The system requirements for Visual Studio 2015 can be found on the Visual Studio 2013 System Requirement page.
Visual Studio provides cutting-edge tools and technologies to create apps that take advantage of the latest platforms capabilities. Visual Studio 2013 also targets earlier platforms such as Windows XP and Windows Server 2003 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 2013. For more information, see Managing Project References and Visual Studio Multi-Targeting Overview.
Visual Studio 2013 Support for Windows Desktop Development
|Targeted Platform 1||Native Code Development||Managed Code Development|
|Windows 8.1||✔️ 2||✔️ 2|
|Windows 8||✔️ 2||✔️ 2|
|Windows Vista||✔️ 5||✔️ 5|
|Windows XP||✔️ 4||✔️ 4, 5|
|Windows Server 2012 R2||✔️ 2||✔️ 2|
|Windows Server 2012||✔️||✔️|
|Windows Server 2008 R2||✔️||✔️|
|Windows Server 2008||✔️||✔️|
|Windows Server 2003||✔️ 3, 5||✔️ 4, 5|
1. Visual Studio supports the listed platforms when used with the latest available service pack for that platform. For more information, see Microsoft Support Lifecycle.
2. See table below for Visual Studio 2013 support for Windows Store app development, including WinJS development.
3. 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.
4. Requires using Visual Studio managed multi-targeting.
5. Remote debugging and profiling tools not available for targeted platform.
Visual Studio 2013 Support for Windows Store App and Windows Phone Development
You can create Windows Store and Windows Phone apps with the following editions of Visual Studio 2013.
|Express for Windows||Windows 8.1||✔️ 1||✔️||Not Supported 2||✔️ 5, 6, 7|
|Ultimate, Premium, Professional||Windows 8.1||✔️ 1||✔️||Service existing 1, 2, 3||✔️ 4, 7|
|Ultimate, Premium, Professional||Windows Server 2012 R2||Build only 1||Build only||Build only||Build only|
|Ultimate, Premium, Professional||Windows 8||Not Supported||Not Supported||Not Supported||✔️ 4|
|Ultimate, Premium, Professional||Windows Server 2012||Not Supported||Not Supported||Not Supported||Build only|
Compatibility with Previous Releases
Windows Store app projects for Windows 8.1 and Windows Phone 8.1 cannot be opened in earlier versions of Visual Studio.
You can install and use Visual Studio 2013 alongside Visual Studio 2012. When installed on Windows 8.1, Visual Studio 2012 continues to support creation of Windows Store apps for Windows 8 and Windows Phone 8. In addition, Visual Studio 2012 Update 3 contains improvements for project compatibility between Visual Studio 2012 and Visual Studio 2013, and resolves compatibility issues for Visual Studio 2012 on Windows 8.1.
.NET 4.5.1 is a highly compatible in-place update of .NET 4 and .NET 4.5.
For additional information, see Visual Studio 2013 Compatibility.
When following the supported upgrade paths, your Visual Studio source, solution, 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.
- Upgrade from Visual Studio Team Foundation Server (and Express) 2012 (RTM or any Update) to Visual Studio Team Foundation Server (and Express) 2013
- Upgrade from Visual Studio Team Foundation Server (and Express) 2010 to Visual Studio Team Foundation Server (and Express) 2013
Carrying assets forward
All data in Visual Studio Team Foundation Server (work items, source files, tests and test results, builds, and warehouse data) carries forward when following supported upgrade paths. However, even when following supported upgrade paths, you should take adequate measures to back up and protect your data prior to upgrading to a new release.