set File Version VIProductVersion

[hanen.jomaa]

Hi,

can you help me please,

I want to have the properties File Version empty ?

How can I do that please ?

[Anders]

The version info resource has a fixed block ( https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx / https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx ) where the file and product version is stored, https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx says that the size of the fixed block can be 0 but NSIS does not support that, your only option is to use 0.0.0.0. It might be possible to use !packhdr and Resource Hacker to get around this NSIS limitation.

You can also set the file version string (VIAddVersionKey) to "" but you cannot control if a 3rd-party application displays the string version number or the number from the fixed block...

[erundil]

Another question.
VIProductVersion sets the Product Version in the file properties window and does not require MUI2.nsh.
Is it possible to set other file properties without MUI2?

What I need specifically is:
File language (must be English), File Description, File Version, Product Name, Legal Copyright and Original Filename.

I know that everything from the list except language can can be set by VIAddVersionKey but it requires MUI2.

[JasonFriday13]

Interesting, Windows 10 does show the language in the details tab. The ones I've checked all say 'Language Neutral'. Perhaps it's a feature not implemented in earlier versions of windows.

[Anders]

MUI is not required to set VI* attributes. VIAddVersionKey /LANG=0 "foo" "bar" will set the string using the neutral language id (in recent NSIS versions) or you can use /LANG=1033 for English etc. (${LANG_ENGLISH} is 1033 and is set by LoadLanguageFile, not MUI) Unless you are setting the version info for multiple languages then the language id used should not matter, Windows will fall back to neutral or English if it does not find something that matches your Windows UI language.

The language is not a real string entry, it is generated by the Windows file properties tab. I believe even Windows 95 does this but the real version tab was removed in Vista and the version info might come from the property system these days.

[erundil]

Originally Posted by JasonFriday13

Interesting, Windows 10 does show the language in the details tab. The ones I've checked all say 'Language Neutral'. Perhaps it's a feature not implemented in earlier versions of windows.

It's there in Windows 7 too.

Originally Posted by Anders

MUI is not required to set VI* attributes. VIAddVersionKey /LANG=0 "foo" "bar" will set the string using the neutral language id (in recent NSIS versions) or you can use /LANG=1033 for English etc. (${LANG_ENGLISH} is 1033 and is set by LoadLanguageFile, not MUI) Unless you are setting the version info for multiple languages then the language id used should not matter, Windows will fall back to neutral or English if it does not find something that matches your Windows UI language.

The language is not a real string entry, it is generated by the Windows file properties tab. I believe even Windows 95 does this but the real version tab was removed in Vista and the version info might come from the property system these days.

Thanks for the quick reply! That's everything I needed to know.