On Nov 7, 2007 5:57 PM, Richard <[EMAIL PROTECTED]> wrote:
>
> In article <[EMAIL PROTECTED]>,
> "Shawn Edwards" <[EMAIL PROTECTED]> writes:
>
> > I have a .wxs file which via candle and light generates a .msi file
> which is
> > 293,915,648 bytes. When I try to sign it using signtool.exe, I get
> this:
> >
> > The following certificate was selected:
> > Issued to: MyCompany Inc.
> > Issued by: VeriSign Class 3 Code Signing 2004 CA
> > Expires: 5/28/2008 5:59:59 PM
> > SHA1 hash: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
>
> You'll have to split some of the file payload out into an external
> CAB file and sign the CAB file separately. Its a known issue with the
> signing tool.
Thank you for your quick response! This is good and bad news; good to know
that I'm not doing something wrong, but...
I believe you that's it's a known problem, but my customer doesn't. They
want an explanation/bug report/knowledge base article/note from Bill Gate's
mom/etc. Do you know of somewhere this has been discussed in the past?
Thanks again for your help.
--
Shawn Edwards
Beware programmers with screwdrivers. Or, for that matter, any other mixed
drink.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
