Hello all,
I am trying to author a WiX 3.0 merge module (or two if necessary) that
will allow multiple app MSIs to install a Win32 shared SxS assembly and
associated policy (i.e the same deployment strategy that VC++ uses.)
After many attempts I continue to hit two roadblocks:
1) The first app M
I am encountering this recently-reported bug ...
http://sourceforge.net/tracker/index.php?func=detail&aid=2992323&group_i
d=105970&atid=642714
I'm authoring a merge module to install a Win32 shared SxS assembly and
associated policy. Everything works fine for the first MSI that uses it
but the s
an AV app
running? Aaron Stebner's blog has a lot of entries on possibilities for
this, but AV seems more likely in your case.
Phil Wilson
-Original Message-
From: Stephen Paterson [mailto:stephen.pater...@digital-rapids.com]
Sent: Thursday, April 01, 2010 5:13 PM
To: General
install in
WinSxS too) are not available to custom action code on Vista and later
because they're not really available until InstallFinalize and commit.
You haven't said if there are run-time dependencies, and I don't know if
the app and the assembly means 1, 2, and 3, but I think
I'm using WiX 3.0.5419.0 to generate an MSI that installs ...
1) an MFC app
2) the required VC9 merge modules
3) a Win32 shared SxS assembly
4) a DifxApp driver package.
I can build an installer that will successfully install and uninstall
the app and the drive
5 matches
Mail list logo