$VERSIONINFO not behaving as expected (Assuming my expectations are correct)

[hanness]

It's possible I'm simply missing something here since this is the first time I'm using $VERSIONINFO but here is what I am finding:

$VERSIONINFO:FILEVERSION# is working as I would expect. In other words, if I right-click on the resulting executable, select properties, and go to the "Details" tab, I see the "File version" correctly listed there. However, I have tried several other parameters such as LegalCopyright, ProductName, and CompanyName and none of these show any information on that details tab.

Am I misunderstanding how this should work?

Additional Info:

I am running QB64 1.3 on Windows 10 1809 with all the latest Windows updates.

[Petr]

I also tried it under Windows 7. The FileDescription and FILEVERSION# are saved correctly. All other records are missing. The program I ran the test for:

Code: QB64: [Select]

1. SCREEN 0
2. pip
3.  
4. $CHECKING:ON
5. $VERSIONINFO:CompanyName=TEST - Company Names
6. $VERSIONINFO:FILEVERSION#=1,1,5,7
7. $VERSIONINFO:PRODUCTVERSION#=1,2,5,7
8. $VERSIONINFO:InternalName=TEST - InternalName
9. $VERSIONINFO:LegalCopyright=TEST - LegalCopyright
10.  
11. $VERSIONINFO:LegalTrademarks='TEST - LegalTrademarks'
12. $VERSIONINFO:OriginalFilename='TEST - OriginalFileName'
13. $VERSIONINFO:ProductName='TEST - ProductName'
14. $VERSIONINFO:Web='TEST - WEB url:'
15. $VERSIONINFO:Comments='TEST - comments'
16. $VERSIONINFO:FileDescription=TEST - FileDescription
17.  
18. SUB pip
19.     BEEP
20. END SUB
21.  

[FellippeHeitor]

Maybe newer Windows versions just don't have support to *showing* these properties, but they do get saved to the file correctly (something you can check by inspecting the binary itself with something like Resource Hacker - or maybe even a hex viewer).

  [ You are not allowed to view this attachment ]  

[FellippeHeitor]

That also reminds me I forgot to update the version number before we released v1.3! /nervous laughter

[FellippeHeitor]

A bit more info:

When you use $VERSIONINFO, all QB64 does is generate a text file with the information you added, which is the same we do when $EXEICON is used. The file, called a resource descriptor, can be found under internal/temp/icon.rc. You can inspect it to see that we are following Microsoft's format as seen here: https://docs.microsoft.com/en-us/windows/desktop/menurc/versioninfo-resource

It's the job of the C++ compiler to actually embed the icon/version information into the final binary. Whatever's not showing is, as I said, simply not showing, but it's surely there.

[Petr]

Thank you for answer, Fellippe. It's not the first time, when Windows don't show something. But if Source Hacker it show, it is Windows problem. Nothing that would surprise me with Microsoft. 

[hanness]

I guess that there must be different ways storing that information. I notice that some other executables from various programs do show that information. I don't know if Windows maybe gets that information from a different location.

So clearly, however they are storing that information, Windows is able to read it.

[hanness]

Sorry, I should have included a screenshot of an example. Below is screenshot showing what the installer for the latest version of VMware Workstation Pro looks like:

[FellippeHeitor]

Hummm. Will check.