how to modify properties of final compiled .exe file on the windows standalone platform?

daleksan · Nov 9, 2018

Hi all,
i would like to add information in final compiled application (windows standalone: myapp.exe) about "Copyright" and change file version from unity version to my own.

Is it possible? If yes, how can i do it?

screenshot with that i would like to do is attached:

Thanks in Advance!

Tautvydas-Zilys · Nov 10, 2018

Yes. There is an option to "Generate Visual Studio Solution" in the build window. Instead of generating final executable, it generates a visual studio project that builds the final executable. You can then change it in whatever way you want.

daleksan · Nov 10, 2018

Tautvydas-Zilys said: ↑

Yes. There is an option to "Generate Visual Studio Solution" in the build window. Instead of generating final executable, it generates a visual studio project that builds the final executable. You can then change it in whatever way you want.
Click to expand...

Thank you so much. i dit it. I created visual studio solution from unity. Modified "WindowsPlayerVersion.rc" and got it.

daleksan · Nov 11, 2018

Well. I work on integration this in TeamCity.
Tautvydas-Zilys, Do you know the way how to create visual studio solution for windows standalone through command line?

Tautvydas-Zilys · Nov 11, 2018

Yeah, it's non-obvious. You can do it like this:

Code (csharp):

EditorUserBuildSettings.SetPlatformSettings("Standalone", "CreateSolution", "true");

You could also rebuild the executable once, and then commit it to your source control and just overwrite the one from the regular build - it should make your build faster.

Cybernetic_Nick · Feb 20, 2020

Tautvydas-Zilys said: ↑

Yes. There is an option to "Generate Visual Studio Solution" in the build window. Instead of generating final executable, it generates a visual studio project that builds the final executable. You can then change it in whatever way you want.
Click to expand...

Is this still possible in Unity 2019.3? I am able to open the build in Visual Studios, but I am unable to locate and update the WindowsPlayerVersion.rc?

I do see that WindowsPlayer.rc has a line of code that includes "WindowsPlayerVersion.rc", and that the Windows PlayerEngine located in the Unity Editor application folder has a file named "WindowsPlayerVersion.rc" but I am unable to change that file.

What is the best approach for updating this file within Visual Studios to where I can still rebuild the project for distribution?

Thank you.

Tautvydas-Zilys · Feb 20, 2020

Cybernetic_Nick said: ↑

Is this still possible in Unity 2019.3? I am able to open the build in Visual Studios, but I am unable to locate and update the WindowsPlayerVersion.rc?

I do see that WindowsPlayer.rc has a line of code that includes "WindowsPlayerVersion.rc", and that the Windows PlayerEngine located in the Unity Editor application folder has a file named "WindowsPlayerVersion.rc" but I am unable to change that file.

What is the best approach for updating this file within Visual Studios to where I can still rebuild the project for distribution?

Thank you.
Click to expand...

Nothing changed in 2019.3. It's still there:

It references it from the project directory, not from Unity Editor application folder.

Cybernetic_Nick · Feb 21, 2020

Tautvydas-Zilys said: ↑

Nothing changed in 2019.3. It's still there:
View attachment 564439

It references it from the project directory, not from Unity Editor application folder.
Click to expand...

Thank you for your help. I was trying to find this file within the Visual Studios solution but it was not showing up within the IDE's Resource View panel, and then I must have overlooked it when checking through the directory.

localprojects · Apr 3, 2020

Hi,

Thank you for the info. got it working.

I just wanted to confirm this is the only way(compile solution and then change) and that there is no other automation-friendly way, and also wanted to ask the reason the version number doesn't cascade from the app/unity version number.

Thank you

Tautvydas-Zilys · Apr 3, 2020

localprojects said: ↑

I just wanted to confirm this is the only way(compile solution and then change) and that there is no other automation-friendly way, and also wanted to ask the reason the version number doesn't cascade from the app/unity version number.
Click to expand...

It does cascade from Unity version. By default, the version field will be the same as the Unity version.

Automation friendly way: do the change manually once, commit it to your repository and then have automation either build or copy it.

hanidahanib75 · Apr 17, 2020

i want to ask how i can open this file if my computer using 32 bit

RambosRide · Apr 12, 2022

While I can generate a .sln file - I'm no C++ expert and without documentation on what to change in WindowsPlayerVersion.rc -- everything I've tried just corrupts the WindowsPlayerVersion.rc file and I have to start over again. There must be more documentation out there but I can't find it?

Tautvydas-Zilys · Apr 12, 2022

RambosRide said: ↑

While I can generate a .sln file - I'm no C++ expert and without documentation on what to change in WindowsPlayerVersion.rc -- everything I've tried just corrupts the WindowsPlayerVersion.rc file and I have to start over again. There must be more documentation out there but I can't find it?
Click to expand...

It's a standard Windows Resource file, and the format is documented by Microsoft: https://docs.microsoft.com/en-us/windows/win32/menurc/about-resource-files

RambosRide · Apr 12, 2022

View Code: WindowsPlayerVersion.rc

#include <windows.h>
#include "UnityConfigureRevision.gen.h"
#include "UnityConfigureVersion.gen.h"
#include "UnityConfigureOther.gen.h"

VS_VERSION_INFO VERSIONINFO
FILEVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN,UNITY_VERSION_BLD
PRODUCTVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN,UNITY_VERSION_BLD
FILEFLAGSMASK 0x17L
#ifdef _DEBUG
FILEFLAGS 0x1L
#else
FILEFLAGS 0x0L
#endif
FILEOS 0x4L
FILETYPE 0x0L
FILESUBTYPE 0x0L
BEGIN
BLOCK "StringFileInfo"
BEGIN
BLOCK "040904b0"
BEGIN
VALUE "FileVersion", UNITY_VERSION_WIN
VALUE "ProductVersion", UNITY_VERSION_WIN
VALUE "Unity Version", UNITY_VERSION_UNDER_HASH
END
END
BLOCK "VarFileInfo"
BEGIN
VALUE "Translation", 0x409, 1200
END
END

How would I add UNITY_COPYRIGHT as it isn't populated with this code?

Tautvydas-Zilys · Apr 12, 2022

Something like this:

Code (csharp):

#include <windows.h>

#include "UnityConfigureRevision.gen.h"

#include "UnityConfigureVersion.gen.h"

#include "UnityConfigureOther.gen.h"

VS_VERSION_INFO VERSIONINFO

FILEVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN,UNITY_VERSION_BLD

PRODUCTVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN,UNITY_VERSION_BLD

FILEFLAGSMASK 0x17L

#ifdef _DEBUG

FILEFLAGS 0x1L

#else

FILEFLAGS 0x0L

#endif

FILEOS 0x4L

FILETYPE 0x0L

FILESUBTYPE 0x0L

BEGIN

BLOCK "StringFileInfo"

BEGIN

BLOCK "040904b0"

BEGIN

VALUE "FileVersion", UNITY_VERSION_WIN

VALUE "ProductVersion", UNITY_VERSION_WIN

VALUE "Unity Version", UNITY_VERSION_UNDER_HASH

VALUE "LegalCopyright", "RambosRide (c) 2022"

END

END

BLOCK "VarFileInfo"

BEGIN

VALUE "Translation", 0x409, 1200

END

END

That section is documented here: https://docs.microsoft.com/en-us/windows/win32/menurc/stringfileinfo-block

RambosRide · Apr 13, 2022

That's the information I couldn't find I didn't know to look for "StringFileInfo" - Thank you!

RambosRide · Apr 14, 2022

IDK if I'm doing something wrong but if I comment out
FILEVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN,UNITY_VERSION_BLD
On the compiled exe the File Version gets set to 0.0.0.0 and not the FileVersion in StringFileInfo.

In the Screen grab you can see it still shows unity FILEVERSION, not MY_VERSION

I can override the FILEVERSION values but would have thought the StringFileInfo:FileVersion would populate that field.

Unity version 2020.3.25f1

Tautvydas-Zilys · Apr 14, 2022

I think those are two separate properties, and Properties dialog only shows one of them. If you used a tool that showed full information, you'd probably see both. You'll have to change FILEVERSION if you want it to show up in the Properties dialog.

RambosRide · Apr 14, 2022

Thanks for confirming the issue.

I will modify the FILEVERSION as suggested.

I really appreciate the help!

RambosRide · Sep 27, 2022

When we went to 2021.3.4 the windowsstandalone visual studio sln project was changed (still using VS2019)
When I compile now the ProductVersion displaying odd character, in code I use the same constant I use for File Version which does display correctly - any ideas? Thanks!

VALUE "FileVersion", UNITY_VERSION_WIN
VALUE "ProductVersion", UNITY_VERSION_WIN

- please see attached pic.

Tautvydas-Zilys · Sep 27, 2022

I think the issue is that UNITY_VERSION_WIN is a number while it is expecting a string. Try replacing it with

Code (csharp):

""

or

Code (csharp):

"My Product Name"

Alternatively you could completely delete that line from the .rc file.

stfunity · Oct 23, 2022

Tautvydas-Zilys said: ↑

I think the issue is that UNITY_VERSION_WIN is a number while it is expecting a string. Try replacing it with

Code (csharp):

""

or

Code (csharp):

"My Product Name"

Alternatively you could completely delete that line from the .rc file.
Click to expand...

I found this thread partially helpful but in my result build from the Visual Studio SLN Unity outputs, it breaks my references to streaming assets. This is a Windows exe build.

The directory structure of the output builds is that standard build/bin/x64/Master, which I suspect is problematic because I want my result application to look -just- like a Unity build i.e. the app sits next to its _Data folder in the root of the application, not 4 directories up and around the corner. So, if I put the x64 exe output into the root where it should be, I lose all my speech recognition models in StreamingAssets under the _Data folder.

What do I do about that? How can I make the structure proper?
My builds straight from Unity have no such issue, but then my app properties are generic and come with a Unity copyright stamp and I don't want that.

Catch 22 so far, search queries on this subject lead nowhere because if you look up "unity visual studio build streamingassets path issues/wrong/structure/etc" you get nothing specific from those search queries and all the various issues people cite are absolute red herrings for my current problem. This is the only thread I've learned much of anything from that contains these terms

Silly to me because why bother entering my Company and Product info if it's not going to be appended to the output build Exe from Unity?

Going over to VSCode where they don't care if I lose my streamingassets when they make my "fancy" exe with 6 string properties reassigned [heaven forbid] seems like it shouldn't be the move but here I am.

Tautvydas-Zilys · Oct 24, 2022

So first of all, yes, Visual Studio solution builds a little different folder structure. Instead of the usual:

Code (csharp):

Game_Data

Game.exe

UnityPlayer.dll

You get:

Code (csharp):

Game_Data

<ARCHITECTURE>\<CONFIG>\Game.exe

<ARCHITECTURE>\<CONFIG>\UnityPlayer.dll

What this allows doing is sharing the same data folder for several different game build configurations: you might want to ship both 32-bit and 64-bit player and duplicating the data folder would double the size of your game. This allows you only have one copy of it. It also makes builds faster because Unity and Visual Studio does not need to copy the data folder into each possible configuration output folder.

You can take all the files from "x64\Release", move them 2 directories up and get rid of architecture specific folders. You could also just do normal builds from Unity, and replace the resulting .exe after the build with the one that you premade from a built Visual Studio project previously.

That said, I don't understand how this breaks your streaming assets. Are you calculating the paths yourself or something? Application.streamingAssetsPath should point to the right folder regardless of how the build is made.

stfunity said: ↑

Silly to me because why bother entering my Company and Product info if it's not going to be appended to the output build Exe from Unity?
Click to expand...

I think it sets the game title in the titlebar and also uses that information to compute log paths and Application.persistentDataPath.

stfunity · Oct 26, 2022

Tautvydas-Zilys said: ↑

So first of all, yes, Visual Studio solution builds a little different folder structure. Instead of the usual:

Code (csharp):

Game_Data

Game.exe

UnityPlayer.dll

You get:

Code (csharp):

Game_Data

<ARCHITECTURE>\<CONFIG>\Game.exe

<ARCHITECTURE>\<CONFIG>\UnityPlayer.dll

What this allows doing is sharing the same data folder for several different game build configurations: you might want to ship both 32-bit and 64-bit player and duplicating the data folder would double the size of your game. This allows you only have one copy of it. It also makes builds faster because Unity and Visual Studio does not need to copy the data folder into each possible configuration output folder.

You can take all the files from "x64\Release", move them 2 directories up and get rid of architecture specific folders. You could also just do normal builds from Unity, and replace the resulting .exe after the build with the one that you premade from a built Visual Studio project previously.

That said, I don't understand how this breaks your streaming assets. Are you calculating the paths yourself or something? Application.streamingAssetsPath should point to the right folder regardless of how the build is made.

I think it sets the game title in the titlebar and also uses that information to compute log paths and Application.persistentDataPath.
Click to expand...

It's hard to say -why- but basically after attempting the build like this and having no visible errors, the built app cannot access the StreamingAssets path, but inside Unity everything works perfectly. I can't tell what parameters might have been altered or whether Plastic SCM isn't detecting a difference, but even with rollback attempts, the results are the same now.

If I attach a debugger to the build, it just indicates "model of model provider is null" out of the Vosk/Recognissimo libraries

We had this same sort of error last week on an unrelated path on our Mac Studio running 2022.1.16f1 - before any of this came up, and to solve it we had to upgrade Unity to 2022.1.20f1 and that stopped the inexplicable "no streaming assets found at [the path is valid ?!, it's right there why is it null]"

So I am not even sure if the issue is strictly related to any attempt to build VS Solutions out of the project. The project worked fine for months, then stopped having Speech Recognition on builds on the Mac suddenly, only solved by upgrading Unity 0.04 versions. Then we thought everything was good, then I tried to customize the App Details on Windows and otherwise found this thread helpful, except then the same error on a totally different platform.

Details are scant on why.

One thing I can tell you is on the PC here after this Solution build attempt, Unity now adds the WinPixEventRuntime.dll to my build folder, which it never did before. I don't tend to run debug builds.

Not sure if any of those facts are clues but like I said, same TYPE of error but seemingly different cause on Mac vs Windows, on Mac, upgrading solved it. The other workstations were upgraded to match, then after VS build, PC goes down with the same problem and Mac version build is unaffected.

And for the record, all the code I write and the code in the packages I'm using for Speech Recognition all refer to "Application.streamingAssetsPath" or "Application.persistentDataPath" explicitly rather than some hardcoded path.

Tautvydas-Zilys · Oct 26, 2022

stfunity said: ↑

One thing I can tell you is on the PC here after this Solution build attempt, Unity now adds the WinPixEventRuntime.dll to my build folder, which it never did before. I don't tend to run debug builds.
Click to expand...

WinPixEventRuntime.dll is used by development builds, which map to "Release" configuration in Visual Studio. To build non-development builds, use the "Master" configuration.

P_e_t_a_c_h_e_k · Oct 30, 2022

Tautvydas-Zilys said: ↑

WinPixEventRuntime.dll is used by development builds, which map to "Release" configuration in Visual Studio. To build non-development builds, use the "Master" configuration.
Click to expand...

Good evening, your answers helped me a lot, I just posted a question, could you please look at it?
https://forum.unity.com/threads/pro...ild-the-project-through-visualstudio.1355114/

philipgen · Nov 4, 2022

Hello, I am using Unity 2021.3.9f1 and Visual Studio 2019
I created the solution and modified the WindowsPlayerVersion.rc by Notepad and just changed the values.

Code (CSharp):

#include <windows.h>

#include "UnityConfiguration.gen.cpp"

VS_VERSION_INFO VERSIONINFO

FILEVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN

PRODUCTVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN

FILEFLAGSMASK 0x17L

#ifdef _DEBUG

FILEFLAGS 0x1L

#else

FILEFLAGS 0x0L

#endif

FILEOS 0x4L

FILETYPE 0x0L

FILESUBTYPE 0x0L

BEGIN

BLOCK "StringFileInfo"

BEGIN

BLOCK "040904b0"

BEGIN

VALUE "FileVersion", "2.10.0.10800"

VALUE "ProductVersion", "2.1.0"

VALUE "Unity Version", "2021"

END

END

BLOCK "VarFileInfo"

BEGIN

VALUE "Translation", 0x409, 1200

END

END

But when I rebuild the solution in Visual Studio and check the exe file. I'm still getting empty values.

Tautvydas-Zilys · Nov 4, 2022

Can you show the full WindowsPlayerVersion.rc file after your edits?

philipgen · Nov 4, 2022

It's in my previous post. All I did was change the value of the FileVersion, ProductVersion, Unity Version

Code (CSharp):

#include <windows.h>

#include "UnityConfiguration.gen.cpp"

VS_VERSION_INFO VERSIONINFO

FILEVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN

PRODUCTVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN

FILEFLAGSMASK 0x17L

#ifdef _DEBUG

FILEFLAGS 0x1L

#else

FILEFLAGS 0x0L

#endif

FILEOS 0x4L

FILETYPE 0x0L

FILESUBTYPE 0x0L

BEGIN

BLOCK "StringFileInfo"

BEGIN

BLOCK "040904b0"

BEGIN

VALUE "FileVersion", "2.10.0.10800"

VALUE "ProductVersion", "2.1.0"

VALUE "Unity Version", "2021"

END

END

BLOCK "VarFileInfo"

BEGIN

VALUE "Translation", 0x409, 1200

END

END

Tautvydas-Zilys · Nov 4, 2022

You might have to change these too:

Code (csharp):

FILEVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN

PRODUCTVERSION UNITY_VERSION_VER,UNITY_VERSION_MAJ,UNITY_VERSION_MIN

philipgen · Nov 5, 2022

Code (CSharp):

#include <windows.h>

#include "UnityConfiguration.gen.cpp"

VS_VERSION_INFO VERSIONINFO

FILEVERSION 1, 0, 0, 0

PRODUCTVERSION 1, 0, 0, 0

FILEFLAGSMASK 0x17L

#ifdef _DEBUG

FILEFLAGS 0x1L

#else

FILEFLAGS 0x0L

#endif

FILEOS 0x4L

FILETYPE 0x0L

FILESUBTYPE 0x0L

BEGIN

BLOCK "StringFileInfo"

BEGIN

BLOCK "040904b0"

BEGIN

VALUE "Comments", "Tenta a tua Sorte!"

VALUE "CompanyName", "Adsglobal"

VALUE "FileDescription", "Jogo Simples"

VALUE "FileVersion", "1.0.0.0"

VALUE "InternalName", "Tenta a Sorte"

VALUE "LegalCopyright", "Copyright © Rodrigo Santos 2020"

VALUE "OriginalName", "Tenta a Sorte"

VALUE "ProductName", "Tenta a Sorte"

VALUE "ProductVersion", "1.0.0.0"

END

END

BLOCK "VarFileInfo"

BEGIN

VALUE "Translation", 0x0816, 1200

END

END

No. I did it like this and I am still getting empty results. I even started with a brand new Unity 2021.3.9f1 project.

philipgen · Nov 7, 2022

Turns out it does work.
Before, for some reason, when I build in my folder that is linked to my cloud account, (Box.com), I was unable to see the properties.
I then built it on a local folder, (C:\temp\), and it works perfectly.

RambosRide · Nov 17, 2022

Tautvydas-Zilys said: ↑

I think the issue is that UNITY_VERSION_WIN is a number while it is expecting a string. Try replacing it with

Code (csharp):

""

or

Code (csharp):

"My Product Name"

Alternatively you could completely delete that line from the .rc file.
Click to expand...

Sorry for delayed response.. this fixed the problem. Thanks!

foozuu · Dec 7, 2022

https://github.com/electron/rcedit
I prefer to use this, especially when you already have a auto pubulic work flow

Gaspedal · Jan 26, 2023

I simple use the resource hacker tool for my exe files, very easy to use and works fine ^^
open the exe file -> edit -> compile script -> save as new exe file or replace.
But it would be great when we can edit this in player settings before we compile.

http://angusj.com/resourcehacker/

daddycaddy · Nov 16, 2023

Hi was going through the steps in this forum but when i tried to build my project through the Sln i got these errors

Tautvydas-Zilys · Nov 16, 2023

daddycaddy said: ↑

Hi was going through the steps in this forum but when i tried to build my project through the Sln i got these errors
Click to expand...

You should be able to right click on the solution file in the solution explorer and press "Retarget solution".

Search Unity

Unity ID

Useful Searches

how to modify properties of final compiled .exe file on the windows standalone platform?

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Attached Files:

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies