Issues and limitations

The following is a list of known issues and limitations with the Microsoft GDK Tools package.

Issues

• The Microsoft GDK Tools package does not currently support the Windows build setting Create Visual Studio Solution.
• You must manually create or copy a valid MicrosoftGame.config file alongside the installed Unity.exe in order to use the GDK in Play Mode.
• The Unity Editor might require a restart to recognize changes to the MicrosoftGame.config file when used in combination with the built in editor player.
• When creating a package build, you must manually increment the version number in the Identity element of the MicrosoftGame.config file. Make sure the version number follows Microsoft's guidelines on Package Version Numbering.
• When targetting headless CI EditorUserBuildSettings.GetBuildLocation(StandaloneWindows64) can return an empty string in some situations causing MakePri.exe to fail a work-around is to call EditorUserBuildSettings.SetBuildLocation(buildTarget, buildPath) first before starting the build process.
• Build for GDK automatically adds/removes the MICROSOFT_GDK_SUPPORT pre-processor to the list of player defines, however it can not account for the player defines being manually changed outside the scope of the tools package.