Re: The problem with GetFileVersionInfoSize
- From: "Michael Salamone" <mikesa#at#entrek#dot#com>
- Date: Mon, 21 Jul 2008 19:35:38 -0700
As you've found, yes of course you can include version resources just like any other resource type.
WinCE OS executables don't have version resources, so you can't view them for OS modules. Doesn't stop you from including them yourself in your own application.
--
Michael Salamone, eMVP
Entrek Software, Inc.
www.entrek.com
"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:C3F6622C-C20B-4875-91AE-C35C8AB53E96@xxxxxxxxxxxxxxxx
By the way I've checked exes on my PC built for Mobile 5.0 and Win CE 6.0.
Both of them contains version info.
"Steve" wrote:
Thank you for response.
Is it still possible to force linker to include version resource in exe
under Win CE?
"r_z_aret@xxxxxxxxxxxx" wrote:
> On Mon, 21 Jul 2008 04:58:00 -0700, Steve
> <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >By the way searching the MSDN newsgroups I found the following:
> >
> >"By old tradition, WinCE program files do not contain version > >resources,
> >because storage on WinCE device is scarce. "
> >
> >Does it meant that exe I built simply doesn't contain version > >resource?
> >If this is true then why GetFileVersionInfoSize function supported > >under
> >WinCE?
> >How to force linker to include version resource in exe under Win CE?
> >
> >Can anyone comment?
>
> My experience has been that the info _is_ included in the exes, and
> has been since Windows CE 2.0. You can check by looking at the
> properties of your exes (in "big" Windows, right click on the name of
> an exe and then pick "Properties"). But it isn't visible under CE!
>
> The related functions were definitely not supported under Windows CE
> 2.0. I haven't checked for a while. This link is to a library that I'm
> pretty sure includes substitutes.
>
> >
> >Thanks
> >
> >"Steve" wrote:
> >
> >> I have MFC dialog based application. I build the application > >> targeting custom
> >> Win CE 6.0 based SDK.
> >>
> >> I don't understand why but the following code segment caused > >> application to
> >> crash at runtime:
> >>
> >> wchar_t fileName[] = TEXT("\\Program Files\\TestApp\\TestApp.exe");
> >> DWORD tmp = 0;
> >> DWORD size = ::GetFileVersionInfoSize(fileName, &tmp ) ;
> >>
> >> Obviously since I successfully passed compilation and linking steps, > >> the SDK
> >> I target supports this function.
> >>
> >> Can anyone explain or give me hint what is goin wrong with
> >> GetFileVersionInfoSize?
> >>
> >> Thanks
> >>
> >> P.S. The similar problem I experience with CryptUnprotectData > >> function.
>
> -----------------------------------------
> To reply to me, remove the underscores (_) from my email address (and > please indicate which newsgroup and message).
>
> Robert E. Zaret, eMVP
> PenFact, Inc.
> 20 Park Plaza, Suite 478
> Boston, MA 02116
> www.penfact.com
>
.
- References:
- Re: The problem with GetFileVersionInfoSize
- From: r_z_aret
- Re: The problem with GetFileVersionInfoSize
- From: Steve
- Re: The problem with GetFileVersionInfoSize
- From: Steve
- Re: The problem with GetFileVersionInfoSize
- Prev by Date: Re: Linker error when including shlwapi.h
- Next by Date: StartUp Problem
- Previous by thread: Re: The problem with GetFileVersionInfoSize
- Next by thread: StartUp Problem
- Index(es):
Relevant Pages
|