You can add signing in the wixproj but I couldn't get that to work and in my
case I needed to use signtool as the certificate is not in the certificate
store. This is the approach I used (I can't remember to originator of this but
it was someone on this list):
1. insignia -ib Setup.exe -o engine.exe
2. signtool engine.exe (extra parameters excluded for simplicity)
3. insignia -ab engine.exe Setup.exe -o Setup.exe
4. signtool Setup.exe
(insignia is part of the wix toolset.)
Neil
-----Original Message-----
From: Rob Diaz [mailto:[email protected]]
Sent: 20 April 2012 23:05
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Burn feedback
I agree that I've had similar troubles. The lack of documentation has made
this tougher to do than it should be.
Did you find a resolution for the signtool issue? Other than not doing it, I
mean.
Rob
-----Original Message-----
From: Neil Sleightholm [mailto:[email protected]]
Sent: Friday, April 20, 2012 5:33 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn feedback
Sounds like the same issues I have been having, I am planing to blog about what
I have found to help others. Thanks for the LicenceUrl tip, I had missed that
and ended up writing my own theme based on the HyperlinkLecense one.
Neil
Neil Sleightholm
[email protected]<mailto:[email protected]>
On 19 Apr 2012, at 17:34, Pally Sandher wrote:
I upgraded to WiX v3.6 from v3.5 earlier this week and started trying to
implement Burn as a replacement for dotnetinstaller.
So far it's pretty easy to get a chain of packages configured & I really like
how well done it is (great job everyone involved =) ).
A few of the issues I've noticed with it (using v3.6.2816.0):
Documentation is very sparse but I guess it's still under construction so it's
forgivable but still causes a lot of grief when you're basically left with
reverse engineering to discover how to implement things.
It makes it very hard to get anywhere with customising it when this is all the
documentation you have to follow
http://wix.sourceforge.net/manual-wix3/wixstdba_foundation_customization.htm
I had to download the sources just to figure out what size to make the logo
which this page says you can customise
http://wix.sourceforge.net/manual-wix3/wixstdba_branding.htm since it isn't
mentioned anywhere.
http://wix.sourceforge.net/manual-wix3/wixstdba_license.htm says you can have
"unlicensed" installation experience if you don't provide a value for the
LicenceUrl attribute when using
WixStandardBootstrapperApplication.HyperlinkLicense. What you actually have to
do is set the value to " " as you get the following errors when you attempt to
build is you try to use "":
The bal:WixStandardBootstrapperApplication/@LicenseUrl attribute's value cannot
be an empty string. If you want the value to be null or empty, simply remove
the entire attribute.
The bal:WixStandardBootstrapperApplication element must have a value for
exactly one of the LicenseFile or LicenseUrl attributes.
WixStandardBootstrapperApplication.HyperlinkLicense provides an Options button
which does pretty much nothing. There's no (easy) way to hide this button which
I've found so far. I don't appear to be the only one on this list with the same
enquiry.
Variable names cannot contain '.' which meant lots of fun when trying to check
for existing installations of .NET 4.0 Client Profile before I learned this
through trial & error. The bundle will build completely fine & then fail when
you try to run it. You should not be able to build a bundle which fails to run
because of the Variable names, as these are simple enough to check at build
time.
Using Signtool.exe to sign the Burn output causes it to fail when run. I only
figured this out through searching list posts. OMFG this was a serious waste of
time & had me running in circles trying to figure it out for half a day before
I stumbled across the information. This needs to be writ large across the Burn
documentation so others don't fall foul of the same issue along with
documentation on how to code sign Burn bundles properly.
Intellisense doesn't work in WiX 3.6 using the installer. I think Neil
Sleightholm mentioned the fix is to copy the intellisense files from the
binaries so it seems like a packaging issue with the WiX 3.6 installers but has
been a problem since the RC0 release & still exists 2 weeks & 2 builds later.
Quiet/passive and silent install modes would be nice (dotnetinstaller supports
these). I don't see any way to set launch options for ExePackage elements to
specify these type of scenarios. Good for saving time when checking builds &
when automated deployment tools are used etc.
That's it so far.
Palbinder Sandher
Software Platform Engineer
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the <Virtual Environment>** Integrated
Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered
Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP Email Disclaimer
----------------------------------------------------------------------------
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------------
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
