You might consider, for a per-machine setup, installing a 'template' to a single location under CommonAppDataFolder\somefolder (typically C:\ProgramData\...).
Design the application so that if it needs to write user specific information, it should manage reading the default template and writing the user specific data to the user's area (typically i C:\Users\<username>\...) . When a new version is deployed to CommonAppDataFolder the application needs update any specialized copies it created in a user's space. This is the approach which we are using successfully. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Accessing-files-copied-to-the-ProgramFiles-folder-during-the-installation-tp7600401p7600406.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
