is are encoded in a way that is not as simple as
just removing the braces and dashes from the GUID, so I would suggest searching
for the target path instead. Then you'll at least know whether leftover
reference counts are the problem. Just make sure that they don't legitimately
belong
ponents have a different ID.
>
> And some more info on the location of the stored references and how
> the GUID's are compressed:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Windows-
> Installer-Service-and-reference-counting-td702967.html
>
>
>
rent ID.
And some more info on the location of the stored references and how the GUID's
are compressed:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Windows-Installer-Service-and-reference-counting-td702967.html
-Original Message-
From: Scott Moyer [mailto:scott.mo...
I found some "Disallowing uninstallation of component: {} since another
client exists" messages in the uninstall log, which look to be referencing the
exe files, but can't find any references to the those guids in my MSI or in the
Registry. They are not from a merge module, and I have never used
I do not see anything suspect in the install log.
Components that get removed say 'Action: Absent' in the uninstall log.
Components not getting removed have 'Action: Null' in the uninstall log.
Also Registry entries are not being removed ('Action: Null'), even when using
SharedDllRefCoun
-ons.aspx
-Original Message-
From: Scott Moyer [mailto:scott.mo...@appliedvision.com]
Sent: Monday, March 24, 2014 11:50 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] What is the best way to design a Bootstrapper
requiring external input ?
Thanks for the r
our main MSI install to then allow this aux bundle
to plan the proper driver MSI.
As for the remember me property pattern,
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern
-Original Message-
From: Scott Moyer [mailto:scott.mo...@appliedvision.com]
Sen
Thanks for the reply.
I already have four MSIs for the two drivers (two x64 and two x86), and I am
familiar with passing variables from a BA to an MSI. I just need to figure out
how to pass information back from the MSI so the BA can access it. I do not
understand how to persist a variable and
First of all, I think WiX is pretty awesome, but I am having some trouble
understanding how to implement some of the advanced customization/extension
capabilities, and what is the best way to design and implement ...
My new assignment wants me to modernize and cleanup a 15-year old IS6 install
. There is no way for Packages to communicate Properties back to the Bundle.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-----
From: Scott Moyer [mailto:scott.mo...@applied
I am not understanding examples on how to set a bundle version from the version
of an exe file.
I did so very simply in my msi as shown below:
...
...
...
But can't figure out how to do the same for a Bundle that cont
ssage-----
From: Scott Moyer [mailto:scott.mo...@appliedvision.com]
Sent: Monday, March 10, 2014 1:58 PM
To: 'WiX-users@lists.sourceforge.net'
Subject: [WiX-users] Bootstrapper question
Does anyone know if a Bundle/Chain can access a public property from a bundled
msi?
In the followi
Does anyone know if a Bundle/Chain can access a public property from a bundled
msi?
In the following example the CAMERATYPE property is set in Genius.msi ...
http://schemas.microsoft.com/wix/2006/wi";>
Thanks!
NOTICE:
Does anyone know a way to dynamically create a dialog depending on a property
setting. Looks like you can perform a condition on a Control but not on a
specific RadioButtonGroupI could create a custom action to present the dialog
but would prefer not to. If necessary will just create an entirely
14 matches
Mail list logo
