Hi,
I have a problem with my patching mechanism in WIX.
The problem is,
There were some manual patches given to the customer. i.e to
manually copy the config and executable files
Now when they apply the patch made by WIX technology, this patch
is not copying the manually
My product has some 32-bit files installed on both platforms and some
64-bit files only for x64 platform. And installation is shipped in two
languages: en_US and pl_PL (files are the same, but one registry entry
differs).
So basically I have four packages:
MyProduct.En.32.msi
MyProduct.En.64.msi
It sounds like you need Burn, but it is not there yet. I had a similar
problem to yours and used the MS Build GenerateBootstrapper task to create a
.exe bootstrapper for each MSI output. So I had
MyInstaller.[Lang].[Architecture].exe as well as
MyInstaller.[Lang].[Architecture].msi. The
I've read
http://robmensching.com/blog/posts/2003/10/18/Component-Rules-101
and I'm still confused about something. Suppose a component gets
installed more than once, but to different places. This can happen if
several product installers include the same component (same component
GUID,
I've used the free utility 'RegSpy' to capture .reg files for my COM servers
(exe, dll, and tlb). It works well.
Ken
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, February 01, 2010 12:48 AM
To: sean.far...@seanfarrow.co.uk; General discussion for
Windows Installer registers components using the component GUID, ProductCode
and key path to the component. So for files, each instance of the
component, based on ProductCode registers with its own path. The component
can be registered more than once to the same path as well but each instance
Hi,
I've asked about similar issue a few days ago (on 7th January 2010):
http://n2.nabble.com/Question-about-Shared-Components-and-their-Key-Paths-td4265681.html#a4265681
There is a blog post mentioning the components are tracked for each
product independently:
I'd second the recommendation of RegSpy, it's worked pretty well for
me in the past.
Do keep in mind that you should tweak the the wxs file to resolve
things like file references before you start building with it.
--Nathan
On Mon, Feb 1, 2010 at 9:09 AM, Ken Halprin khalp...@autosoln.com wrote:
Hi,
Can we use torch.exe and pyro.exe in WIX2.0?
Thanks Regards,
Srivardhan.
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the
Hi,
This is a noob question, but I did not find an easy way of doing this.
I have a custom property element:
Property Id=radioButtonSelectedSystem Value=0 /
which is linked to a radio buttons group on a custom dialog in order to
select a desired system.
Depending on what the user
Do not use 0 as a value for a property. It's used as NOT set for the
property, like as well. I tend to you yes and no strings directly to
reflect booleans.
Best regards,
Sebastian Brand
sebast...@instyler.com
Instyler Software - Software development, deployment and productivity
Geisenfelder
Yep, it's set correctly.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Saturday, January 30, 2010 6:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] File association description
Did you verify that the ProgId
I'd add use RegSpy to generate a .reg file, then tallow from WiX2 to
generate a wix fragment, then wixcop from v3 to update it. A bit long
winded but you only need to do it once or twice.
Neil
-Original Message-
From: Ken Halprin [mailto:khalp...@autosoln.com]
Sent: 01 February 2010
It's been a long time since I've used WIX, so it's almost like starting
over again. I thought I'd restart my education by using dark.exe to
decompile some of our existing MSIs, but every time I run the one that
was installed by the WiX v3.0 installer, it abends with:
dark.exe : error DARK0001 :
My apologies for not being complete. That is the exact procedure I use and
found it works well.
Ken
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Monday, February 01, 2010 12:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
What is the full version of the WiX toolset are you using?
On Mon, Feb 1, 2010 at 10:21 AM, Houston,Jerry jhous...@vertafore.comwrote:
It's been a long time since I've used WIX, so it's almost like starting
over again. I thought I'd restart my education by using dark.exe to
decompile some of
Torch.exe and pyro.exe require a 3.0 wix.dll (among other files). While you
can't use the WiX MSI to install two builds side-by-side you can use the
binary zip file.
Use the advice on non-WiX inputs to building MSP files with WiX (since 2.0
does not produce .wixpdb files).
-Original
Summary:
I'm struggling to figure out the WiX code and MSI parameters to alter
installed features from the command line.
Details:
I have a WiX-generated MSI with two features, let's call them FeatureA
and FeatureB. I install from a bootstrapper which passes a command-line
parameter indicating
Take a look at the ADDLOCAL property i the MSI SDK.
On Mon, Feb 1, 2010 at 8:38 PM, JKLists jkli...@ifm-services.com wrote:
Summary:
I'm struggling to figure out the WiX code and MSI parameters to alter
installed features from the command line.
Details:
I have a WiX-generated MSI with two
19 matches
Mail list logo
