Visual studio ultimate 2012 requires newer version of windows

The engineering owner of the project type in question looks at these criteria and makes the call where support, compatibility, and migration are concerned. Again, Visual Studio tries to maintain transparent compatibility between Visual Studio versions if possible, meaning that one can create and modify projects in one version of Visual Studio and it just works in other versions.

If such compatibility is not possible, however, as with some of the project types described in this article, then Visual Studio opens the upgrade wizard to make the necessary one-way changes.

Such one-way changes may involve changing the ToolsVersion property in the project file, which denotes exactly which version of MSBuild can turn the project's source code into runnable and deployable artifacts that you ultimately want. That is, what renders a project incompatible with previous versions of Visual Studio is not the Visual Studio version, but the MSBuild version, as determined by ToolsVersion.

So long as your version of Visual Studio contains the MSBuild toolchain that matches the ToolsVersion in a project, then Visual Studio can invoke that toolchain to build the project. To maintain maximum compatibility with projects created in older versions, Visual Studio includes the necessary MSBuild toolchains to support ToolsVersion 15, 14, 12, and 4. Projects that use any of these ToolsVersion values should result in a successful build.

Subject, again, to whether Visual Studio supports the project type at all, as described on Platform Targeting and Compatibility. In this context, the question naturally arises whether you should try to manually update or migrate a project to a newer ToolsVersion value.

Making such a change is unnecessary, and would likely generate many errors and warnings that you'd need to fix to get the project to build again. Furthermore, if Visual Studio drops support for a specific ToolsVersion in the future, then opening the project will trigger the project migration process specifically because the ToolsVersion value must be changed. In such a case, the subsystem for that specific project type knows exactly what needs to be changed, and can make those changes automatically as described earlier in this article.

Each new version of Visual Studio supports most types of projects, files, and other assets. You can work with them as you always have , provided that you don't depend on newer features. If you're looking for information specific to our next release, see the Visual Studio version of this page. We try to preserve backwards compatibility with previous versions, such as Visual Studio , Visual Studio , Visual Studio , and Visual Studio However, support for some project types changes over time.

A newer version of Visual Studio might not support certain projects at all, or it might require that you update a project so that it's no longer backwards-compatible. For current status on migration issues, refer to the Visual Studio Developer Community.

And to learn more about which features are specific to which Visual Studio version, see the Release Notes. Some project types require specific workloads. In that case, check your installation options in the Visual Studio Installer and try again. For more information about project support in Visual Studio , see the Platform Targeting and Compatibility page. If you don't see a project or file type listed here that should be, consult the Visual Studio version of this article.

While we try to maintain compatibility with previous versions, there can be changes that aren't compatible with previous versions. When this happens, a newer version of Visual Studio won't load the project or offer a migration path.

You might have to maintain that project in a previous version of Visual Studio. Sometimes, the newer version of Visual Studio can open a project, but it must update or migrate the project in a way that might render it incompatible with previous versions.

The engineering team that owns the project type looks at these criteria and makes the call where support, compatibility, and migration are concerned. Again, we try to maintain compatibility between Visual Studio versions so that when you create and modify projects in one version of Visual Studio, it just works in other versions.

Sometimes, compatibility isn't possible. Then, Visual Studio opens the upgrade wizard to make the necessary one-way changes. These one-way changes might involve changing the ToolsVersion property in the project file, which denotes exactly which version of MSBuild can turn the project's source code into the runnable and deployable artifacts that you want.

If your version of Visual Studio contains the MSBuild toolchain that matches the ToolsVersion in a project, then Visual Studio can invoke that toolchain to build the project. To maintain compatibility with projects that you created in previous versions, Visual Studio includes the necessary MSBuild toolchains to support ToolsVersion 15, 14, 12, and 4. Subject, again, to whether Visual Studio supports the project type, as described on Platform Targeting and Compatibility.

You might be tempted to manually update or migrate a project to a newer ToolsVersion value. It's unnecessary to make such a change, and would likely generate many errors and warnings that you must fix to get the project to build again. Also, if Visual Studio doesn't support a specific ToolsVersion in the future, then the project triggers the project migration process when you open it because its ToolsVersion value must be changed.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Tip If you're looking for information specific to our newest release, see the Visual Studio version of this page.

Important Certain project types require installing the appropriate workloads through the Visual Studio installer. Tip If you're looking for information specific to our next release, see the Visual Studio version of this page.

Important Some project types require specific workloads. Submit and view feedback for This product This page. View all page feedback. In this article. Projects created with Visual Studio used preview tooling that included an xproj project file. In Visual Studio , the xproj format is not supported other than for migration to csproj format.

When you open an xproj file, you're prompted to migrate the file to the SDK-style csproj format. A backup of the xproj file is made. SDK-style csproj projects are not supported in Visual Studio and earlier. For more information, see Migrating. NET Core projects to the csproj format. For each Visual Studio user, resource information is stored in the registry per user instance. Visual Studio includes all the tools necessary to be able to create all kinds of projects for Microsoft operating systems, but furthermore, it's also perfectly capable of creating websites or, even, programs for mobiles and tablets.

Thanks to the elements that are part of Visual Studio any programmer will have the possibility to complete a full project without any need to resort to other programs or external elements. The graphical environment of Visual Studio has undergone a change, being very similar to the Metro graphical interface and the general product line that Microsoft had already marked after launching Microsoft Office Preview , even though it does maintain the code color identification which so many users demanded after they had originally left it out of the Beta version of the program called Visual Studio Beta.

Download Visual Studio to design your own programs for Windows 8 Vote 1 2 3 4 5 6 7 8 9 Requirements and additional information:. This download requires an Internet connection to install the application. The trial version can be used for 30 days. I already installed every update on Operating system. What have I do to install VS Ultimate? It is clearly stated by Microsoft that only 4 Windows releases are supported by Visual Studio , and Windows Server non-R2 is not qualified,.

How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 8 years, 10 months ago. Active 6 years, 9 months ago.

Viewed 13k times. You must upgrade or update Operating Systems to the latest Service Pack using Window Update to meet the requirement before installing this products.