An older version of our product was installed with Internet Component Download.
Part of the install copied a .DLL to System32.
Our MSI installer of a newer version of the product copies the same version of
the DLL (it's a shared component that hasn't changed in a long time) to
System32. If t
I've got an MSI (that's somewhat polished, thanks to this list!) using the
AssemblyApplication parameter on the File tag for "autohealing" and dependency
tracking. An example is shown below:
Installing on Vista requires administrative privileges, because we write to a
subfolder in
You'll need to grab the registry information out of regasm and convert it into
a WiX-friendly syntax. This is done at design time, not on the final machine.
For a mostly automated process, you'll need tallow from the WiX 2.0 toolset,
and then some mystery executable I can't remember :) to conv
> Recently I have faced with the same issue. According to my research, as
> also Bob said, you can ignore the warning LGHT1056, I think it just
> tries to make msi author think twice before deploying into SystemFolder.
> In our case while merging modules like mscomctl, mscomct2, msvbvm6, etc.
> the
Sorry about that, Bob. Mis-click of the reply button.
These are the official merge modules from Microsoft for VS6.
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 12, 2007 10:49 PM
To: Bryan C. Boettcher; WiX-users
Subject: Re: [WiX-users
Can I not deploy files to System32?
S:\release\cabs\product.msi.wxs(15) : warning LGHT1056 : The Directory table
contains a row with primary key(s) 'SystemFolder' which cannot be merged from
the merge module 'S:\build\msm\comcat.msm'. This is likely due to collision of
rows with the same prima
I'm packaging shared components in my MSI. These components (like COMDLG32.OCX
or MSCOMCTL.OCX) are installed into %system32%. However, I've got an issue
with the files not upgrading properly. I always want to have the newest
version of the shared component on the machine. As per my last que
We have a somewhat unique requirement for our product. Concurrent versions
need to be made available on a single machine. We have a matched client and
server, for which the protocol changes each version. One desktop machine might
need to talk to 5 differently-versioned servers, and will need
8 matches
Mail list logo
