I have written an Outlook add-in (VSTO in C#) and now the problem occurs that on some machines (all Windows 7) with Office 2010 installed the Outlook add-in suddenly becomes inactive after a Windows Update (including at least one Office update).
It can be reactivated without any issues though and everything will be working fine, including the user-settings.
Do you know what could cause this behavior?
Thanks.
Related
I work on an add-in for Microsoft Outlook, and recently we’ve received reports from some users that they can no longer click on buttons in the taskpanes of add-ins. Other add-ins, not just ours, have been affected by this issue. Affected users can still open the taskpane without issue. Our taskpane web view loads correctly, but then any clicking inside the taskpane has no effect. We are not seeing console errors when this happens.
To help narrow things down further: we’ve seen this issue occur in Outlook 2019 and Outlook for Microsoft 365 MSO with Office 365 accounts so far. We’ve seen this issue happen when the taskpane is opened from Compose view. One affected user was using Outlook 2019 version 16.0.13127.20266 (32-bit). Affected users have been running Windows 10, version 2004. A team member was able to reproduce the bug by updating to version 2004, but the bug disappeared for them after a subsequent system update on the same version 2004.
Has there been any recent change to add-in taskpane behavior that could be causing this issue?
This issue was fixed, and the fix should be available in Windows build 19043.1266 or later. Note that it is the Windows Build that matters, not the Office build.
We are seeing the same thing since updating to Windows 10 build 2004. For us, the add-in task pane freezes when the user tries to reply to an email (which is also compose view I guess).
Would be good to get an update on this as it is breaking the add-in for our users.
We are using Outlook Version 2009 (Build 13231.20200)
This is Outlook for Microsoft Office 365 MSO (16.0.13231.20146) 64 bit.
I have written a VSTO for Outlook with a formregion for meeting/appointmentitems in VS 2015.
I deploy this to our desktop computers using ClickOnce.
I would like to use the Windows Installer to install the VSTO for laptops because when I use ClickOnce and the laptop uses Outlook when not connected to the corporate network, the add-in is disabled.
I assume this is because it cannot reach the internal ClickOnce publish location, eventhough the deployment should not check for updates.
I have followed this article to create an installer for the addin.
I followed the all-users steps and the files are installed to the local computer and the registry keys are being created but the Add-in is not loaded in Outlook and it even is not showing up in the list of Addins in Outlook.
Anyone who has had similar issues and knows how to solve this problem? It's driving me crazy for the past 2 days.
There is no such central repository. Your addin most likely gets disabled on startup because of a run-time error.
We developed an Outlook Add-In for Win 7 with SP1 and .NET Framework 4.0 as a prerequisite. It gets install perfectly on some machine without any hiccup but in other machines (same configuration, Win 7 & SP1) the add-in goes into the 'inactive' state and doesnt load while outlook start-up.
While installing there are no issues or error message getting displayed. What could be the problem? How can I check or debug what could be causing this issue? Any solution or hints on this will be highly appreaciated.
Inactive add-ins are usually caused by a missing reference that wasn't deployed. Try some of these resources:
http://blogs.msdn.com/b/haahmadi/archive/2010/05/26/my-vsto-add-in-does-not-load.aspx
http://archive.msdn.microsoft.com/vstotroubleshooter
I am developing a VSTO 2010 Office 2007 Outlook Add-In deployed from Click-Once. On the computer I developed it, running Visual Studio, everything works just fine, but when trying to install it on another computer, the addin is installed, and during the startup screen, It comes under Inactive Applications Add-in.
In Load Behavior, It shows Not Loaded.A Runtime error Occured during the loading of the COM-Add-in.I have changed the Load behavior from 2 to 3 in HKCU under Registry Editor.But it is again reverted back to 2.Not sure how to find the specific error so I can fix it.
Does anyone have any ideas on what might be causing this?
Any ideas anyone might have would be greatly appreciated.
Finally I have found a solution by myself.What I have done is Before I published a solution I was checked .Net Framework 3.5 SP1 Client Profile in prerequisites under Install settings and it works for me now.
We have an issue with an Outlook 2007 AddIn (created on a Windows 7 development machine with Visual Studio 2008/VSTO).
It installs with the MSI installer on these machines:
- the development machine
- a Windows XP machine
Install initially succeeded on a Vista machine, but after installing an updated version of the AddIn, it gets disabled when starting Outlook. We suspect it might be related to how Vista handles security.
Have anyone encountered issues specific to installing VSTO AddIn on a Vista machine?
(Please note that the AddIn in our case gets installed alright, but is 'just' disabled when starting Outlook.)
The add in might be throwing an exception.
An unhandled exception causes the add in to be disabled.
We hit this issue on some random machines and after much head scratching, it turned out that Office.Interop was not installed on the client. We had assumed it would be installed with Office 2007 - which it appears to be in many cases.