Hi Grant,
You then have two items in the Add/Remove programs, one for the installer project and one for the VSTO addin. Is that correct?
Actually this is caused by a small bug from Advanced Installer. Normally the first install, the one created with Advanced Installer should handle all the settings,
including the ones done by the second installer, the one that runs when you start the Office app. A fix has been implemented and will be available with the next version of Advanced Installer. Until than you can apply the solution explained by me here:
http://www.advancedinstaller.com/forums ... 212#p50212
This confuses me as I use the property based folder in the native addin to load a file into it. A custom action script runs before that to populate the session property for that folder.
Probably the custom action is not scheduled correctly. Have you tried executing it before the costing operations?
The keys you've enumerated are the correct ones for the current version of Office, however for older versions like 2003 additional keys are required. This why I recommended you simply use the "Import MSI" feature from Advanced Installer in your native addin project, to get the contents of the MSI created for the VSTO addin. Have you tried that?
Regards,
Bogdan
FOLLOW US
Get the latest news in Application Packaging