John-Daniel Trask wrote: > You mention there is no guarantees with this process. Does this mean there > would be a more robust mechanism of achieving the same outcome? Would > bootstrapping and then manifesting the bootstrapper in a manner that > elevated permissions resolve this issue more? >
Nope, it's not a permissions problem. Basically, the problem with commit custom actions is that they rely on MSI's rollback support being enabled; it is by default, but it can be disabled. When rollback is disabled, commit custom actions are just skipped with no errors. In that situation, your VSPackage won't be registered at all. The guidance to put VSPackages in the GAC should carry big disclaimers. In general, a private assembly in some Program Files directory is the best because it won't have the risks with the GAC. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
