Using XNA Game Studio with Visual Studio 2012 (or higher) |
Microsoft XNA Game Studio only supports Visual Studio 2010. Later version of Visual Studio are only partially supported (only Windows Phone 7 projects). Here is a list of workarounds to use the Microsoft XNA Game Studio with Visual Studio 2012 and higher.
This topic contains the following sections:
Follow these instructions to use XNA Game Studio with Visual Studio 2012 (or higher).
Copy the folder named XNA Game Studio 4.0 from
to
On some systems Visual Studio is incorrectly installed in the Program Files (x86) folder instead of the Microsoft Visual Studio 12.0 folder. In this case you have to use this target path: C:\Program Files (x86)\Common7\IDE\Extensions\Microsoft
to
This works for Visual Studio Professional. If you use an edition that is not listed, you might have to add a tag for this edition. For example, for Visual Studio 2013 Premium or Ultimate change
<SupportedProducts> <VisualStudio Version="10.0"> <Edition>VSTS</Edition> <Edition>VSTD</Edition> <Edition>Pro</Edition> <Edition>VCSExpress</Edition> <Edition>VPDExpress</Edition> </VisualStudio> </SupportedProducts>
to
<SupportedProducts> <VisualStudio Version="12.0"> <Edition>Ultimate</Edition> <Edition>Premium</Edition> <Edition>Pro</Edition> </VisualStudio> </SupportedProducts>
or
and execute
devenv.exe /setup
to rebuild the extension cache.
In some solutions XNA content projects are always rebuilt even if the output is up-to-date - which can be annoying because building content can take many minutes in larger projects. Usually, this happens if a content pipeline project is included in the solution. The content pipeline assembly is updated every time the project is built, which causes the content to be rebuilt.
A simple workaround is to build the content pipeline projects once and then unload it from the Visual Studio solution: In Visual Studio open the Solution Explorer, right-click the content pipeline project and select Unload Project in the context menu.
If this does not solve the problem and the content is still rebuilding, then you can check the Visual Studio build log in the Output window to see which project causes the rebuilds. You might have to increase the amount of information in the build log: Open the menu Tools | Options... | Projects and Solutions | Build and Run and change the MSBuild project build output verbosity to Detailed.