Merge modules are generally now considered bad practice - they become
impossible to service, because the module does not retain its identity. The
only way to service them is to patch the products which have merged the
module. Crystal Reports had a security patch earlier this year:
You have to turn on IIS6 Metabase Compatibility, and rollback is not
supported - because in their infinite wisdom the IIS team didn't implement
all the IIS metabase API, specifically not including the backup and restore
APIs, which the WiX custom actions use to implement rollback. (Reference:
Merge modules are generally now considered bad practice...
If this is true than what is the point of the whole MSI system? I mean if I
have a 3rd party component (x.dll) that 4th party and 5th party are using too,
how does the system decide that the x.dll component installed by the 4th
party's
Hello,
over the last few days I've created a WixExtension to simplify the use
of managed custom actions (immediate and deferred).
See
http://www.infinitec.de/articles/development/wixmanagedcustomactionexten
sion.aspx.
Full source included, published under the same license as Wix (Common
I am Phillip Moore Page Esq. I am reaching out to you as regards the handling
of an investment portfolio.
I am soliciting your assistance in repatriating the funds and property left
behind by my late client before it is confiscated by the government and
declared unserviceble by the bank
I run dark against my MSI, and I get an exception. Ive tracked it down a
bit, and I find that if I delete particular ros in the AppSearch table, I
can get dark to work. Please find an attached MSI that demonstrates the
problem. Its 4Mg - Sorry its so big!!
Heres the output from dark
6 matches
Mail list logo
