hello all
i know this can be done in a number of ways, and I have already moved to another way of doing it but I am still curious why it doesn't work
please refer to the following post
http://www.advancedinstaller.com/forums ... eal#p50161
in my case though, the self-heal feature kicks in but the file is not created in my %appdata% folder because Windows Installer tries to copy it from the admin's %appdata%
to summarize quickly:
1. user "admin1" installs the MSI which has two features, HKCUFeature and MainFeature. MainFeature is a subfeature of HKCUFeature. The only component in HKCUFeature is the file "config.ini" which is located under Application Data\ConfigF
2. the file "config.ini" is correctly copied under admin1's %appdata%\ConfigF
3. user "user1" then logs on to the same workstation and double-clicks the advertised shortcut on the StartMenu. Self-heal kisks in and fails (as evident from the Event log). The event says that the file C:\Users\admin1\AppData\Roaming\ConfigF\config.ini does not exist which is understandable since user1 does not have access to admin1's user profile folder
4. when I search the registry for this component, I see it's registered and the path is the same as above: C:\Users\admin1\AppData\Roaming\ConfigF\config.ini
why is it that Windows Installer tries to copy the file from admin1's %appdata% folder and not the cached MSI, and more importantly, how to modify my package so I can achieve the desired result?
thanks much
FOLLOW US
Get the latest news in Application Packaging