Good point, but at this point I'm happy to have something that works at all.
It's really just a stop-gap to get us through this upgrade cycle and won't
be needed once everyone is on perMachine.
-Dave
On Mon, Feb 23, 2009 at 6:52 PM, Bob Arnson wrote:
> Dave Wright wrote:
>
FYI, I finally did get this working. I had to move the Custom Action to the
UI sequence so that the uninstall would run before the install sequence
started. Seems to be working OK now.
-Dave Wright
On Mon, Feb 23, 2009 at 2:29 PM, Wilson, Phil wrote:
> That's correct, and you may want
Unfortunately it doesn't look like my idea to use MsiConfigureProduct in a
custom action is going to work - it's not allowed and complains that an
installation is already in progress. How would I use a bootstrapper to get
around this limitation?
-Dave Wright
On Sun, Feb 22, 2009 at 2:0
Thanks, I was afraid of that. I'll look into using
MsiEnumRelatedProducts. Would the correct procedure be to then simply
call:
MsiConfigureProduct(product, INSTALLLEVEL_DEFAULT, INSTALLSTATE_ABSENT)
..in order to uninstall the previous product prior to install?
-Dave Wright
On Sun, Feb 22,
opposed to resorting to scripting if that's what it will take to get
it done.
Note that I don't expect it to ever work properly if you're installing
the upgrade from a different account than the original perUser install
- I just need the upgrade to work properly from at least that acco
5 matches
Mail list logo
