First let me get this stuff out of the way:
- This happens with my own addin, as well as another third party VSTO add-in, so I don't think I'm doing anything incorrect
- .net 4.0. VSTO runtime 10.0.50701
- Windows 8. Also tried Windows 7
- I am using the
|vstolocal
suffix in the HKLM registry for the addin - I have also tried adjusting the 'program files' paths in the registry here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
to point to my new 'F:' location, and that didn't change any behavior
Here are the steps I'm taking:
- Create a new volume on a separate disk other than C:. I called mine 'F:'
- Add the program files structures F:\program files and F:\program files (x86)
- Install your VSTO addin (I'm using Outlook but it will happen with Word too) to "F:\program files (x86)" instead of the 'C:' drive
- Launch Outlook.
Result is this dialog:
According to this, I shouldn't be getting this since its an all users install (see the Inclusion List section):
Is this a Microsoft issue? I realize I can add to the Inclusion myself however then I would be subscribing to more of a per-user approach, and that seems like a bad approach. Is this coming up because anything other than the 'real' program files folder cannot really be trusted by VSTO loader?