hi all! (this being my first post to the list) i'll cut to the chase, what is the best way to achieve the following functionality:
- initial install should be by administrator. (as we need to create directories/keys all users should have access to). - the product is updated frequently, but only a few files need changing (mainly the main executable and related help files). - non-administrators should be able to install these upgrades. the entire package is simple (a thick-client): a few files need to go into program files - all users share them, BUT 1 - the software needs to work with with both per-user and per-machine registry keys, 2 - it needs to uses a cache directory, also shared by all users, the path to which is a per-machine setting that should be configurable by any user... you get the idea oh yeah, it would be nice if the same package could handle upgrades and installs to virgin boxes... again the question: what is the best way to go about this? any input is greatly appriciated! ps: i have been reading up on the subject, but had a hard time digesting the info i could find... also didn't find any template quite matching my problem, which is why i'm now humbly turning to this List :-) ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
