Visual Studio 2017 XNA Setup


This guide is a modified version of the guide available here:

  1. Download a modified version of MXA Game Studio, which is a set of installers for adding XNA to Visual Studio.
  2. After downloading, unzip the file
  3. The unzipped folder contains 4 folders. Each one contains an executable. Run them in order:
    1. DirectX\DXSETUP.exe
    2. XNA Framework 4.0 Redistribution\XNA Framework 4.0 Redist.msi
    3. XNA Game Studio 4.0 Platform Tools\XNA Game Studio Platform Tools.msi
    4. XNA Game Studio 4.0 Shared\XNA Game Studio Shared.mxi
  4. Double-click XNA Game Studio 4.0.vsix.
    1. Verify your version of Visual Studio is selected
    2. If you get a message stating “The following extensions are not compatible with Visual Studio 2017”, click Yes – the installation will still work.
  5. Create a new folder: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\XNA Game Studio
  6. Copy everything from
    C:\Program Files (x86)\MSBuild\Microsoft\XNA Game Studio
    C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\XNA Game Studio

    1. 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
    2. 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.
  7. Optional: For TeamCity automated builds, also copy to
    C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Microsoft\XNA Game Studio
  8. Open the start menu and search for Developer command prompt for VS 2017
  9. Right-click on the result and select “Run as administrator”

  10. Execute the following code: (this will add the new version of 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).


Note that the bug is tracked here: