When you build a Unity project to the Windows standalone platform Unity produces the following files (where ‘ProjectName’ is the name of your project):
ProjectName.exe
- The project executable. This contains the program entry point which calls into the Unity engine when launched.
UnityPlayer.dll
- this DLL contains all the native Unity engine code. It is also signed using the Unity Technologies certificate, allowing easy verification that the engine was not tampered with.
*.pdb files
- Symbol files for debugging. Unity copies these to the build directory if you enable Copy PDB files in the Build Settings window.
WinPixEventRuntime.dll
- This DLL enables Windows PIX profiler support. Unity only creates this file if you check the Development Build checkbox in the Build Settings window.
ProjectName_Data folder
- This folder contains all the data needed to run your project.
Unity creates the source code for ProjectName.exe
in this folder: Editor\Data\PlaybackEngines\WindowsStandaloneSupport\Source\WindowsPlayer.
To modify the executable, or ship code which you built yourself (if you want to sign it, for example), you must rebuild the executable and place it in your built game directory.
To build your executable outside of Unity, you need Visual Studio 2015 or 2017 with ‘Common Tools for Visual C++’’ and ‘Windows XP support for C++’ installed.
2017–07–19 Page published with limited editorial review
Windows standalone Player build binaries changed in 2017.2 NewIn20172
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Is something described here not working as you expect it to? It might be a Known Issue. Please check with the Issue Tracker at issuetracker.unity3d.com.
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information