These sound like odd requirements to me. But that said, I'd use the
action states of the components to figure this out. If you want to
consider it from the first-installed product perspective, it will have
to poke in and know at least one of the merge module's components (or
perhaps create a config
you can combine both workarounds given by me before...guess it will resolve
ur problem in ur scenario
On Tue, Mar 9, 2010 at 4:06 PM, akash bhatia <911ak...@gmail.com> wrote:
> if you have different install directories for all then may be u can check
> for the files existed before uninstalli
if you have different install directories for all then may be u can check
for the files existed before uninstalling.
On Tue, Mar 9, 2010 at 3:15 PM, Lisa Gracias wrote:
> Thanks for that idea. It's much simpler than my approach.
> There's an additional condition: The warning should be displayed o
Thanks for that idea. It's much simpler than my approach.
There's an additional condition: The warning should be displayed only if the
product being removed is the one that first installed the merge module,
because only then will it have the shared components in its folders. How do
I find out which
Lisa,
Best way is that u can write a custom action at uninstall which checks
whether other two products r installed or not... set a property for tht
if it found other products then it means tht shared files wont get deleted
from target machine. and u can populate messagebox accordingly (as per th
I have 3 msi's which contain the same merge module. Apart from containing
components common to all 3 products, the merge module also writes an entry
to the HKLM registry hive.
The first product to be installed, say Product A, will put the shared
components in its own folders, and the other two pr
6 matches
Mail list logo
