Tom H.
08-08-2011, 03:38 PM
Hi!
I've been having issues with the SB7 code signing process crashing on me. I been working around them, but figured it was time to report it.
Windows 7 Enterprise
winsdk_web (.NET 4) (code signing DLLs from MS SDK 4, no Capicom.dll needed)
SB7.5.3378.0
Code signing works fine when SB7 is first opened. If I make changes to the script, at least half of the time the script compiler will fail after invoking SignTool with an Error = 2.
Unfortunately, after the error/failed compile it puts the SB7 IDE into an unstable state, either crashing it right there or failing on the next compile. Restarting the SB7 IDE doesn't usually stop the SignTool errors, so I'm sure the MS has something persistent going on as well (probably .NET 4 related.)
Restarting the Win7 VM lets me compile multiple releases within the script without any issues, as long as I don't make changes.
I hope this is clear enough.
Thanks,
Tom
I've been having issues with the SB7 code signing process crashing on me. I been working around them, but figured it was time to report it.
Windows 7 Enterprise
winsdk_web (.NET 4) (code signing DLLs from MS SDK 4, no Capicom.dll needed)
SB7.5.3378.0
Code signing works fine when SB7 is first opened. If I make changes to the script, at least half of the time the script compiler will fail after invoking SignTool with an Error = 2.
Unfortunately, after the error/failed compile it puts the SB7 IDE into an unstable state, either crashing it right there or failing on the next compile. Restarting the SB7 IDE doesn't usually stop the SignTool errors, so I'm sure the MS has something persistent going on as well (probably .NET 4 related.)
Restarting the Win7 VM lets me compile multiple releases within the script without any issues, as long as I don't make changes.
I hope this is clear enough.
Thanks,
Tom