In article <bay122-ds7e44a9b780fe6af49ee05cd...@phx.gbl>, "Blair" <os...@live.com> writes:
> If you are forced by any other constraint to elevate your setup, make it a > perMachine installation (especially on platforms without UAC) and install > the runtime in SxS "shared" mode (either MSM or EXE installer) which will > allow for the possibility of MSFT servicing of the runtime (which they can't > do in isolated mode). What happens if the application is installed per-user and not per-machine? I would expect the merge module would still place the shared component in the shared area and therefore still require admin priveleges, but the application itself would only be installed for the logged-in user. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/> Legalize Adulthood! <http://legalizeadulthood.wordpress.com> ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users