How can the setting of the trust be so hard to implement? So what else is there to try? I'm getting desperate here. The troubleshooting link targeted a different scenario, namely when the add-in is loaded by OutlookĪnd a runtime error occurs and it gets disabled (wish that was my case, at least I would have a clue). There was an entry about the necessary registry entries but I already have those set.
Native image will only be probed in default load context, like with Assembly.Load(). I get no error statements in the logs, only 4 warnings which is the same warning in 4 different files: WRN: Native image will not be probed in LoadFrom context. Again when I start Outlook the add-in is not loaded. So this assembly gets loaded but the rest of my add-in does not. WhereRefBind!Host=(LocalMachine)!FileName=(InclusionListCustomActions.dll).HTM Here I have a file which logs the loading of the InclusionListsCustomActions.dll (among other files):
The MsiExec.exe dir which, I suppose, logs the execution of the installer. Now, when I installed the add-in something got logged. Added the output of this project to the setup project. Just like b.1)ī.3) I've added a InclusionListsCustomActions project to my add-in's solution just like the tutorial suggests. This is the scenario that I've talked about in my previous posts but I wanted to see if anything gets logged. The add-in is installed but isī.2) I've signed the add-in with a self-signed certificated which I've installed on the client machine under Trusted Publishers and Trusted Root Certification Authorities (for my account, for the admin's account and in the local computer section). Normally, the add-in should be executed without any trusting issues from this dir. I've triedĪll 3 ways of granting trust to my add-inī.1) I've installed it in Program Files which is supposed to be a trusted directory. The add-in is installed but when I start Outlook is not loaded and is not present in the add-ins section. It's like the add-in and all the other assemblies are never loaded.
That's fine.ī) If I deploy my add-in using the windows installer NOTHING gets logged. One of them is OUTLOOK.EXE and in it there is a file that logs the loading of my add-in. This is what happens:Ī) If I deploy my add-in using ClickOnce, 2 dirs are creating in Fusion\Default. I've enabled the Fusion logging mechanism. What am I missing? Is there a log where I can see if any errors are thrown when Outlook starts? I checked the Event Viewer - Application log but there I see only the message generated by the successful installation. I have the registry key HKCU/Software/Microsoft/Office/Outlook/Addins/MyAddin and in there I have the load behaviour set to 3 (even after Outlook starts) and the path to the manifest set to C:\InstallationPath\MyAddin.vsto|vstolocal.Īll the dependencies are installed on the client machine. Not even under the disabled or inactive add-ins. In Outlook's add-ins section my add-in doesn't appear anywhere, I've spent 2 days on this and is driving me crazy. No message is displayed, its just like the add-in was never installed. The add-in is installed but it is not loaded when Outlook is started. I've also signed both the manifest and the assembly using a certificate that I've added on the client machine to the Trusted Publishers (by double clicking it and following the wizard - I don't know if this is important but I mention it). I've also handled the trust part of the installation using inclusion lists as described here: If I deploy my add-in with ClickOnce it works fine but I needed some custom actions during installation so I created an installer for it. I've created an add-in for Outlook 2007 using Visual Studio 2010.