E. Crane Computing Support Forum

daengh

Guest

Re: template.manifest was not found

I'm getting messages in powergen.log at the end of my EXE builds like the following:

Creating Executable
S:\xxxxxxxxxxxx\yyyyyyyy.exe
C:\Program Files\E. Crane Computing\PowerGen Professional\\template.manifest was not found.

The person who looks after the build machine downloaded a 'test' version, but they don't know 'test of what'.

The EXEs seem to work correctly.  Is this error a real problem?  Is it related to the code signing beta?

We're using PowerGen 6.5.0.12 and PB 10.5.1 Build 6551.

Thanks

Phil

Guest

Re: template.manifest was not found

The file is delivered with PowerGen.  I placed a copy of it on ftp.ecrane.com (username and password are 'ecrane') that you can download.

The file is used when creating an EXE with the "New Visual Styles" associated with Windows XP.

Regards,

Phil

daengh

Guest

Re: template.manifest was not found

Thanks, Phil, that did the trick.

>>The file is delivered with PowerGen
unfortunately, the folks installing things on our shared machines don't always know what to install/keep/not delete.  :-(  Like the help file I also got from your ftp site. (thanks again!)

Back in the PB world after a sojourn to Java-land, it's nice to see that good tools that work, like PowerGen, are still available.

cheers!

CGregg

Guest

Re: template.manifest was not found

Just as an aside that fits well in here as it deals with Template.manifest....

I'm in the process of building an MSI Installer for our PB app and found that all exe's must have a Manifest embedded in them detailing 'requestedExecutionLevel' and 'uiAccess' to pass Vista Validation.  I added the following to Template.manifest right after the <assemblyIdentity> section and the apps now pass validation in that regard (I still need to do the digital signing):

Phil

Guest

Re: template.manifest was not found

Thanks Chris,

We look into handling this in the next release.  For now thanks again for the tip.

Regards,

Phil

CGregg

Guest

Re: template.manifest was not found

Phil... does PowerGen have a way of specifying a specific manifest other than template.manifest for each executable?

e.g.  I have a project where I have 8 applications in the one GEN file that all get built together... and I want a separate .manifest for each because I need the "name" property of <assemblyIdentity /> to equal the executable name... or does PowerGen perhaps substitute that info automatically when it embeds template.manifest?

Phil

Guest

Re: template.manifest was not found

Hi Chris,

Its a good question!  Right now the template manifest must have the fixed name.   Sonds like a good idea for an enhancement.

As a workaround perhaps you could invoke PowerGen separately for each application (Pwrgn115 /a=gen_file /a=application) and do a renaming operation between each invocation.

Regards,

Phil

CGregg

Guest

Re: template.manifest was not found

Good call... that's the route I'm going to try.

Having a file select dialogue that allows the user to browse to and select a specific manifest (and of course create a separate line item in the GenFile) for each EXE would be great      :)