Richard wrote: > There are times when I think the "unzip files" approach is legitimate. > > For instance, suppose you have a bunch of data files that represent a > snapshot in time for a dynamically updating service.
Install the initial snapshot as a zip file. The service or custom action will then unpack these files into a *temporary location* (ie. NOT under Program Files). The zip file is tracked and removed. Dumping stuff into Program Files is not the right thing to do. Furthermore, since in your scenario the service will fetch updates from a network resource, why not just have it fetch the initial snapshot in the first place? If it is too big, then it is still valid to store the zip file instead of unpacking it. If the customer wants to completely reset the service, they can just delete all dynamic data in a database, and the service can then repopulate the database as if it were an initial snapshot. No reinstall needed. The *only* place to dump files is in a temporary directory or application's data directory (it is NOT under Program Files). The original post alluded towards dumping files in the installation directory. - Adam -- Mail Etiquette ============== * Quote properly or not at all. Top posters, this applies to you! * When replying to posts on mailing lists, only address the mailing list unless poster explicitly requested you include them in CC ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
