On 19.05.2011 09:16, Igor Stasenko wrote:
On 19 May 2011 08:43, Torsten Bergmann<[email protected]>  wrote:
Marcus wrote
This situation with the thousands of different VMs is *impossible*. We need>to 
fix that.
If on Windows you should really use the installer for Pharo 1.2.2.
from the download page. This will give you the two VM's: standard and Cog
and you can use them to start all images from your HD.

Since both have a different icon (also for the Pharo window)
you always know which one you start/running on.

Just give it a try, its simple.

Since the Pharo.exe and PharoCog.exe also have the version number
in the resource section you can right click on it in explorer
and check which code version/revision they have (see attached screenshot).

Torsten, can you please document somewhere, how you chaging the version info?
Here's how we do it for our application:

rc myApp.rc
ResHacker.exe -addoverwrite myApp.exe, myApp.exe, myApp.res, versioninfo,1,

where myApp.rc is the attached, actual values defined in config.h.
So it's not much magic needed :)

rc can be found as part of Visual Studio, and reshacker is freeware, there's a beta with 64bit exe support.

Cheers,
Henry

#include <config.h>

1 VERSIONINFO
FILEVERSION             VER_MAJOR, VER_MINOR, VER_BASELEVEL, VER_PRODUCTBUILD
PRODUCTVERSION          VER_MAJOR, VER_MINOR, VER_BASELEVEL, VER_PRODUCTBUILD

FILEOS                  0x4
FILETYPE                0x1

{
BLOCK "StringFileInfo"
{
        BLOCK "040904e4"
        {

                        VALUE "CompanyName",            FDDK_COMPANYNAME_STR
                        VALUE "FileDescription",        FDDK_PRODUCT_DESCRIPTION
                        VALUE "OriginalFilename",       FDDK_FILE_NAME
                        VALUE "FileVersion",            FDDK_PRODUCTVERSION_STR
                        VALUE "LegalCopyright",         FDDK_LEGALCOPYRIGHT
                        VALUE "ProductName",            FDDK_PRODUCT_NAME
                }
}

BLOCK "VarFileInfo"
{
        VALUE "Translation", 0x0409 0x04E4
}
}

Reply via email to