Creating metadata files

To include application metadata, we create an application manifest file like those used in Chapter 3, Go to the Rescue!, and Chapter 4, Walk – Building Graphical Windows Applications, when we were building applications using the Common Controls widget set (via Walk and andlabs UI). The contents of the assemblyIdentity instance is used to determine the metadata about the executable. For a platform-independent GUI, the file should look like the following:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
   <assemblyIdentity version="1.0.0.0" processorArchitecture="*" name="Chapter14" type="win32"/>
</assembly>

Don't, however, remove the <dependency> section if you are using Walk, andlabs UI, or another toolkit that needs to have a dependency listed in its manifest file.

To add more metadata that may be useful to users (for example, product name and version) you will need to manually set extra values. The goversioninfo tool from github.com/josephspurrier/goversioninfo/ is the easiest way to add these values. Be aware that you can only write to the .syso file once, as running these tools again will overwrite the previous content.

To prepare our icon for Windows, it must be converted into a .ico file (the Microsoft icon format). While there are no icon conversion tools pre-installed with Windows, there are many paid-for applications available that will work. If you prefer a free solution, there are websites that offer image conversion services for no cost. If your development platform is Linux or macOS, you could install icotool, which supports the .ico format.

Table of Contents for Creating metadata files

Create new playlist

Sign In

Sign Up

Table of Contents for
Creating metadata files