Re: Digital signing
- From: "Steve Barnett" <noname@xxxxxxxxxxxx>
- Date: Thu, 6 Dec 2007 16:02:38 -0000
"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:OT$HRkAOIHA.5400@xxxxxxxxxxxxxxxxxxxxxxx
"Steve Barnett" <noname@xxxxxxxxxxxx> wrote in message
news:O%23L%236Z%23NIHA.5720@xxxxxxxxxxxxxxxxxxxxxxx
I've got an automated build script that compiles my app and builds thethe
install. As part of the build, my EXE gets signed using signcode.exe and
install digitally signs itself, also using signcode.exe.but
The problem is, if any of this goes wrong, I can't see the output of
signcode.The output is displayed in what looks like a dos window which
immediately closes.
I've tried writing an app that front-ends signcode and redirects stdout,
I don't get any output as signcode appears to be a windows app that just
opens a dos window for output purposes.
Does anyone know how I can get to see the output of signcode.exe?
Here is one way:
http://www.vb-helper.com/howto_capture_console_stdout.html
This works for 'stdout', but not for programs that write to their own
console window. I don't have signcode.exe on this machine to test.
Windows Pipes get a bad rap because of performance issues compared to
other
OSs. This isn't that much of problem since you are only going to use it
infrequently.
However, you said "build script". Are you using VB, VBA, or something
else.
-ralph
Thanks for the reply. I went back to basics to try to work out what was
wrong (I even went as far as coding a dos batch file). Once the batch file
worked, I stuffed the working command line back in to my app and worked back
from there. I swear the command line I ended up with was no different to the
one I started with that didn't work, but now it works.
I'm able to get the results now stuffed out to a file by capturing stdout in
the traditional way (>d:\filename.txt).
I'm now firing off "cmd.exe /c" to run signcode.exe with it's parameters and
redirection. I shell this to get the process id and waitforsingleobject to
wait for it to finish running. Seems to work; just needs a LOT of tidying up
now (such as using COMSPEC rather than hard coding cmd.exe)..
The build script is in WinBatch. I bought this many many years ago and have
clung to it ever since. Ok, it's another "basic" language to learn, but it
serves it's purpose, allowing me to write version numbering information (it
actually writes a .bas module to be included in the compile), compile the VB
app and build the install in one go. No doubts there are better tools
available now, but the scripts are all written and I can't be bothered to
start again.
Steve
.
- Follow-Ups:
- Re: Digital signing
- From: Ralph
- Re: Digital signing
- References:
- OT: Digital signing
- From: Steve Barnett
- Re: Digital signing
- From: Ralph
- OT: Digital signing
- Prev by Date: Re: How do I customize drag image behavior?
- Next by Date: Re: OT: Digital signing
- Previous by thread: Re: Digital signing
- Next by thread: Re: Digital signing
- Index(es):
Relevant Pages
|