Oh, sorry, it's the pre-req that is registering your product. Yeah, this
case is a little screwy if the user chooses to install the pre-req but then
cancels the actual product install. You actually need to uninstall.
On Wed, Apr 10, 2013 at 3:56 PM, ptr wrote:
> It seems like I need to force a
It seems like I need to force a Plan and bail out like you mention.
A simple scenario like this
1) A Custom BA which has a .NET prereq
2) .NET is installed.
3) Customer doesn't agree to our License agreement and hits cancel
It seems like if you simply do a Engine.Quit the bundle is still regard
If you get to Apply() then you need to return Result.Cancel from one of the
callbacks before apply phase is complete to cause rollback.
On Wed, Apr 10, 2013 at 2:41 PM, ptr wrote:
> hey all
>
> I have a custom managed boostrapper that installs .NET4 framework as a
> prereq. Let's call this Our
hey all
I have a custom managed boostrapper that installs .NET4 framework as a
prereq. Let's call this OurProductWix.exe.
Now we have old installshied based installers , let's call it
OurProductSheild.exe
Now consider this workflow
1) User has OurProductShield.exe already installed.
2) User la
4 matches
Mail list logo
