On 23-Aug-11 15:38, Cody Batt wrote:
> Errors went away and now it works! Can anyone shed some light on the
> functional difference between BootstrapperApplication and
> BootstrapperApplicationRef? (ie when to use each?)
The former defines a BA; the latter pulls in a BA defined elsewhere
(WixBalE
On 23-Aug-11 23:26, shengyixing wrote:
> Now what I want is, to display the installation path for those feature, even
> it cannot customize path, thus show its default installation path.
I don't think it's supported. The MSI SDK says:
The SelectionTree control uses the
SelectionPathOn event to
http://boettr.wordpress.com/2010/05/20/simple-way-to-encrypt-app-config-through-wix-3-5-and-vs2010-using-c-code/
Ran across this tonight too that looks pretty useful :-), I have been meaning
to do something similar for a while now.
I ran across this blog tonight while reading about Lab Management. There are a
couple of entries near the top that might be useful.
Just thought I'd share.
John
--
EMC VNX: the world's simplest storage, starting und
Good evening
I'm trying to get a simple managed UX example working without much success. The
resulting EXE keeps loading the prerequisite bootstrapper that wants to install
.NET 4. The error is:
Loading prerequisite bootstrapper application because managed host could not be
loaded, error: 0x80
I think the fact that the file is edited after it is laid down on the
computer means the install considers the file to be "customer data" because
its Modify date is later than the Create date. That follows the file
versioning rules for unversioned files.
One way around that problem is to specify a
Good afternoon
I'm spending the next couple of days investigating Burn in order to ditch our
custom C++ bootstrapper. I like what Burn appears to offer.
When I try to use a UX DLL that targets the .NET Framework 4, the EXE that Burn
outputs won't even launch. The error log in %TEMP% shows:
[4A
I do not know how to "specify a version on the File element" as I do not see a
version addtibute in the File element.
However I have noticied the following... I do have a version specified in the
Product element. If the version increases, the new file will replace the old
one.
However, I do no
1 - wrong list, this is the users list. This sort of post belongs on the
WiX-devs list.
2 - you'd be better placed submitting a feature request on SourceForge (or
CodePlex if the issue tracker has been migrated over, last time I checked we
were still using SourceForge for issue tracking).
3 - if
Good evening,
Could one of you WiX developers please integrate UPX
(http://upx.sourceforge.net/) in order to add support for LZMA
compression?
MakeMSI already has UPX support, and has had so for quite some time.
Here's an excerpt from his macro language:
#define+ DLLCA-C_COMPRESS_DLL_COMMAND_LI
did you already consider http://wix.sourceforge.net/manual-wix3/msbuild.htm?
--
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more p
11 matches
Mail list logo