I'm working on a desktop application that uses both common application data (located in \Users\All Users\AppData\) as well as roaming data for the current user of the machine (\Users\\AppData\Roaming).
When the current user installs the application for the first time (I'm using InstallShield 2012), the command app data folder is created and populated and the initial default user data is placed in the users' AppData folder. For the application to function correctly, this initial default user data must exist.
However, when another user logs on to the same machine, the required user AppData folder does not exist.
My question is, what is the best way to resolve this scenario? Perhaps the installer needs to populate the '\Users\Default\' folder? Is this even the responsibility of the application, or should a network administrator ensure the folder is populated for multiple users?
It can be done using the installer by authoring per-user components and triggering repair through an advertised shortcut, COM activation or the trick shown here if those don't work for you.
But truthfully, I try to avoid authoring per-user components whenever possible. I find it better to install the resources in a per-machine location and then let your application rather then the installer handle seeding any required user data.
