In article <[EMAIL PROTECTED]>,
"Wilson, Phil" <[EMAIL PROTECTED]> writes:
> If it works deferred on Vista it should work deferred on other OS
> versions too.
I agree with this. The reason you bump into deferred vs. immediate
questions is because you CA is trying to do something that requires
the execution context of the MSI service. Priveleges are elevated for
the MSI service execution context, as opposed to the immediate
execution context which will be the execution context of the user
running the installation.
If your CA is modifying something on the system (changing files,
changing the registry, changing permissions on an object, etc.), then
it should most certainly be in the deferred context so that it will
have the appropriate priveleges *and* you should implement rollback
behavior for the CA so that when the install transaction fails and
your CA changes need to be "undone", you will restore the previous
state of the machine.
This transactional nature of Windows Installer is crucial for CAs and
most people blow it off, but by doing that they create subtle problems
for the users of their installation that are difficult to diagnose and
repair.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
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
