Re: PDK 7.0 Fix?

Hi,

Nope, if you say it is so then it is so.

I guess I'm adding 2 + 2 and getting 5.

I have certainly read somewhere in the MS docs that the
Version number
is  4 tuples of .. blah blah .. between 0 and 65525.

The GetVersionInfo functions all return 4 parts of that
type.

I'm also aware that there's more than one way to version an
MS exec (due
to legacy stuff, I think).

Two hours ago I was happy and secure with Version number
handling.

Now I'm having to resist going and messing with Win32::Exe
or some hex
editor just to see what happens. Perhaps with meditation I
could learn
to accept that I was happy with 0 to 65525 before and
nothing has
changed. Do I really need to know anything else? Do execs
with leading
zeros in version numbers run as elevated users under Vista?
I must sleep.

Thanks, As Ever, for clarification

Regards

Mark


Jan Dubois wrote:
> On Fri, 23 Feb 2007, Mark Dootson wrote:
>> I think the real rub is:
>> In the PDK exec stub there is no VS_FIXEDFILEINFO
structure.
> 
> That is not correct; PerlApp and friends all write a
VS_FIXEDFILEINFO
> as part of the VERSIONINFO resource.  Run filever.exe
against a
> PerlApp generated file if you don't believe it.
> 
> filever.exe is part of the "Windows XP Service
Pack 2 Support Tools",
> and can be downloaded from Microsoft.
> 
> Cheers,
> -Jan
> 
> 


_______________________________________________
PDK mailing list
PDKlistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs

Hi,

In the spirit of "I looked it up because it was
there" ......

Taking the a file version of 1.2.3.4

There are three parts of a VERSIONINFO structure that will
be concerned
with this:

two VS_FIXEDFILEINFO members

FileVersionMS  (1.2) - 1 and 2 stored as high order and low
order bytes
of 32 bit value (or maybe the other way round - this endian
stuff
confuses me)
FileVersionLS  (3.4) - 3 and 4 stored as high order and low
order bytes
of 32 bit value

and a StringFileInfo member
FileVersion  (1.2.3.4)

You can put what you like into the StringFileInfo member.
The VS_FIXEDFILEINFO members have to be in the specified
format.

So, PDK is using a single input value to populate all three
because why
would you actually want to put something different in the
StringFileInfo
member (unless you're MS apparantly).

Err - I think that's it.

Jan, any chance of an extra option for FileVersionString
by the time 7.0.x is released?  

Regards

Mark











_______________________________________________
PDK mailing list
PDKlistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs