So I have created my Burn custom bootstrapper application with WPF UI and it
works great! Burn is awesome!
So far, I'm using Burn to chain the install of several MSIs. Now I'm
working on the prereq/bootstrap portion. My application depends on .NET 3.5
and VC++ 2010 runtime. Right now I have thi
The problem appears to be that BinaryKey specification. As the docs say "the
custom action will not be installed into a target directory". You're not
running it from your install directory - you're running it streamed out of the
MSI file's binary table into some temp folder. It's not a type 18.
Hi Guys, I'm trying to add a custom action of type 18, following the steps
described here
http://blogs.technet.com/b/alexshev/archive/2008/02/21/from-msi-to-wix-part-5-custom-actions.aspx
The problem is when executing my app, it doesn't find a dll required to run the
program.
The dll is present
On 01-Sep-11 10:36, tob...@gmx.net wrote:
> correctly resolved to the one set via command line. Is the resolving of path
> in directory not equal for files and shortcuts? since both (file and
> shortcut) tables reference the direcory table in msi, my thought is the
> directoies referenced are resol
Hello,
the verbose log tells me during uninstall (excerpt):
[...]
MSI (s) (FC:DC) [16:27:06:249]: Executing op:
ActionStart(Name=RemoveShortcuts,Description=Removing
shortcuts,Template=Shortcut: [1])
MSI (s) (FC:DC) [16:27:06:249]: Executing op: SetTargetFolder(Folder=23)
MSI (s) (FC:DC) [16:27:06
A verbose log file will tell all.
On Wed, Aug 31, 2011 at 8:26 AM, wrote:
> Hello,
>
> I have a problem when uninstalling a Shortuct, may be someone has
> experienced the same problem and knows a solution/reasion for the behaviour?
> I Did:
> With Wix I create a (non advertised) shortcut the fol
No, unfortunately, that's a weakness in the current documentation. We don't
have a way to specify the "x" in "WiX v3.x".
We renamed "BaseInputPath" to "BindInputPath" in WiX v3.6 (kept backwards
compatibility) and allowed named bind paths. "base path" was a goofy name.
On Thu, Sep 1, 2011 at 5:1
Hi All,
http://wix.sourceforge.net/manual-wix3/specifying_source_files.htm
Indicates it should be possible to bind files with light.exe using named
binder paths:
In source
Command line
light -b foo=C:\foo\ -b bar=C:\bar\ -b foo=D:\
Is this supported in Wix 3.5 (Stable Releas
8 matches
Mail list logo