I have the need to call a custom action in my .NET dll in two places during Install. (Basically prior to "Preparing", and then again late in the install sequence...maybe right-before "Finish Execution".)
So two ideas here:
1) I realize there is an "intended purpose" for the passed "Action" mandatory parameter, but can I re-purpose these to suit my design? That is, can I pass "Uninstall" to my .NET Installer class even if I'm in the middle of an Install or Upgrade...just to differentiate the methods in the class that will be run?
2) I assume it is possible to call the same .NET Installer class multiple times from my Install-package with multiple Custom Actions?
Thanks,
AJ
FOLLOW US
Get the latest news in Application Packaging