This guide is a modified version of the guide available here:
- Download a modified version of MXA Game Studio, which is a set of installers for adding XNA to Visual Studio. files.flatredball.com/content/XnaInstall/XnaForVS2017.zip
- After downloading, unzip the XNAForVS2017.zip file
- The unzipped folder contains 4 folders. Each one contains an executable. Run them in order:
- XNA Framework 4.0 Redistribution\XNA Framework 4.0 Redist.msi
- XNA Game Studio 4.0 Platform Tools\XNA Game Studio Platform Tools.msi
- XNA Game Studio 4.0 Shared\XNA Game Studio Shared.mxi
- Double-click XNA Game Studio 4.0.vsix.
- Verify your version of Visual Studio is selected
- If you get a message stating “The following extensions are not compatible with Visual Studio 2017”, click Yes – the installation will still work.
- Create a new folder: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\XNA Game Studio
- Copy everything or create symbolic link from
C:\Program Files (x86)\MSBuild\Microsoft\XNA Game Studio to
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\XNA Game Studio
- Note that if you are using a different version of Visual Studio you will need to copy the files to the appropriate location. For example, for enterprise, copy the files to C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\XNA Game Studio
- Note that if your Visual Studio is installed in a different directory, you will need to copy the files to the Program Files folder on the appropriate directory.
- Optional: For TeamCity automated builds, also copy to
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Microsoft\XNA Game Studio
- Open the start menu and search for Developer command prompt for VS 2017
- Right-click on the result and select “Run as administrator”
- Execute the following code: (this will add the new version of Microsoft.Build and Microsoft.Build.Framework to the Global Assembly Cache). Note: that you will need to adjust your folder if your Visual Studio is installed on a different directory (such as the D drive).
cd C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin
gacutil /i Microsoft.Build.Framework.dll
gacutil /i Microsoft.Build.dll
Note that the bug is tracked here: https://github.com/Microsoft/msbuild/issues/1831