VersionInfo resource overwritten on deploy

All,

I've set a custom stub file via the "Custom Options" in the deploy wizard.
This new stub has been updated to include our application's custom icon and
version info.

When I deploy, the icon is passed thru, but it appears the version info
resource has been overwritten with "stock" information (though the "original
file name" field correctly reflects the deployed executable file name).

Has anyone else had this problem?  Does anyone have pointers on where to
poke around in the image to change the "stock" information so I don't have
to re-edit the EXE file after a deploy to re-insert our copyright messages,
app descriptions, version numbers, etc.?

Cheers,

--GK

"G Krupa" <[hidden email]> wrote in message
news:3e9dce57$[hidden email]...
> All,
>
> I've set a custom stub file via the "Custom Options" in the deploy wizard.
> This new stub has been updated to include our application's custom icon
and
> version info.
>
> When I deploy, the icon is passed thru, but it appears the version info
> resource has been overwritten with "stock" information (though the
"original
> file name" field correctly reflects the deployed executable file name).

Actually it's overwritten with the version info stored in the image stripper
custom options. In the Custom Options immediately under the custom stub file
path entry that you modified, there is a versionResource entry, which you
can also modify to suit. Should you wish to set the version number(s)
dynamically based on some in-image setting (e.g. a package version), you can
create a custom image stripper by subclassing ImageStripper and overriding
the versionResource method, for example:

versionResource
 | verString |
 verString := MyShell versionString.
 ^(super versionResource)
  productVersion: verString;
  fileVersion: verString;
  yourself


Regards

Blair