I have an issue with my Addin Outlook.
When I open a .msg
If Outlook was opened no problem.
If Outlook was closed my Addin is not loaded like McAfee's Outlook Addin.
But when I close the .msg and open Outlook, McAfee is loaded but my Addin is not loaded.
Do you have some idea how I could always load my addin or by default loaded when I open Outlook.
Thank you.
There are so many reasons why your add-in is not loaded...
Is your add-in listed in the Disabled COM add-ins list?
Microsoft Office applications can disable add-ins that behave unexpectedly. If an application does not load your add-in, the application might have hard disabled or soft disabled your add-in.
Hard disabling can occur when an add-in causes the application to close unexpectedly. It might also occur on your development computer if you stop the debugger while the Startup event handler in your add-in is executing.
Soft disabling can occur when an add-in produces an error that does not cause the application to unexpectedly close. For example, an application might soft disable an add-in if it throws an unhandled exception while the Startup event handler is executing.
When you re-enable a soft-disabled add-in, the application immediately attempts to load the add-in. If the problem that initially caused the application to soft disable the add-in has not been fixed, the application will soft disable the add-in again. Read more about that in the How to: Re-enable an add-in That Has Been Disabled article.
Also you may find the Troubleshooting COM Add-In load failures article helpful.
Related
I was trying to build a simple MS WORD add in,
The home ribbon has been added.
I am getting the message box on the Addin Stated but the home ribbon is not showing.
Even I have configured the things as follows.
For the Addin settings
Inside the MS OFFICE Options
Also I tried to get the logs in the MS WORD UI erros,
I am not getting any errors in MS word application also.
Actually, after closing all the windows and restarting, I am able to see the addin in the home section.
I am trying to deploy an add-in with add-in commands on the desktop version of office 365, using the Centralized Deployment method.
I followed the instructions for Centralized Deployment and the addin appears as "on" in the Office 365 admin center. I used both "Everyone" and "Specific User/Group", but when I open the Word application and go to Add-ins, under "Admin Managed" I see no addins , and the message "No add-ins currently available." The addin is'nt visible neither on Word 2016 Desktop (with subscription) nor Word Online. I have also tried deploying addins from office store using the same method (Centralized Deployment) but they also don't show up.
I have Word version 1708 (8431.2270), and I am using a developer subscription.
Do you have any suggestions to fix it or know why it is not working? Thank you.
Also,
I noticed that I am getting a 403 Error when refreshing the Admin Managed tab (when calling https://euc-word-edit.officeapps.live.com/we/AddinServiceHandler.ashx)
I solved, by enabling Exchange, and my manifest had an issue.
I changed <CustomTab id="HelloWorld" x:type="CustomTab"> to <CustomTab id="HelloWorld"> and it worked.
I try to deploy my Word web add-on that created by Visual Studio 2017 using the Slideloading method.
When I upload the manifest file the message it gives to me seems fine saying:
Get started with your sample add-in!
Your sample add-in loaded successfully. Go to the HOME tab and click 'Show Taskpane' button to get started.
but when I go to use it, it fails saying:
Add-in Error Sorry, but we can't start this app because it isn't set up properly.
Although I followed the sideloading method well and changed the source location default value to: <SourceLocation DefaultValue="https://localhost:44300/App/Home/Home.html" />
Besides this method worked well by OfficeApp manifest.
If you created your add-in using Visual Studio and just want to test it, you can run/load the add-in simply by using F5 (Start) within the Visual Studio project. When you press F5 to start the project, Visual Studio will automatically host the add-in on your local IIS server and will open Word with the Show Taskpane button visible in the Home tab. The Word add-in quickstart describes this process in more detail. (Note: if you're using Visual Studio to run the add-in like I've described here, you shouldn't modify the localhost port number within the DefaultValue attribute of the SourceLocation element in the manifest.)
If you created your add-in using Visual Studio but want to be able to run it by using the Sideloading technique (i.e., without using Visual Studio), then you'll need to deploy the web application portion of the add-in to a web server. In your post, you say that you've specified https://localhost:44300/App/Home/Home.html as the initial page of your add-in. If you navigate to that URL using a web browser, does the page load successfully (with no certificate errors)? If not, that could indicate a problem with your web app -- for example, perhaps there is no web server running at localhost:44300, or perhaps the web server is running but there is no such path as App/Home/Home.html, or perhaps the web server is running and that is a valid path but the add-in web app isn't SSL-secured.
Our Excel 2007 VSTO solution (built in Visual Studio 2010 SP1 using C# 3.5) is published via ClickOnce.
Clients deploy by clicking a URL using Internet Explorer that looks something like:
http://ourserver.com/ouraddin.vsto
It sometimes causes the Program Compatibility Wizard to pop up post-install and display "This program might not have installed correctly ..."
Does anybody know any workarounds?
I found this post which talks about modifying the manifest files, but that seems to apply to regular ClickOnce solutions not VSTO.
How to prevent "This program might not have installed correctly" messages on Vista
I tried using the MageUI app to open the VSTO file and look for a way to embed the supportedOS tags but there was nowhere to put it.
I also found documentation on editing VSTO manifests, but would prefer not going down this route unless absolutely necessary as one would think the publish wizard out of the box should just work.
http://codeidol.com/csharp/c-sharp-in-office/Deployment/Editing-Manifests/
Perhaps there is a way to modify the source VSTO ClickOnce schemas in the build system to avoid editing the manifests as a post-build task?
Any insight would be greatly appreciated!
Thanks,
Chris
I've got a VSTO 3.0 Word addin that I'd like to profile using VSTS Profiler.
When I try to run an instrumenting run with the profiler, though, I get a warning that it can't be instrumented because the Addin DLL is signed, which, from what I know about VSTO, they have to be signed.
Is there any way to "turn off" the signature verification on Word VSTO addins?
Barring that, theoretically, I could NOT sign my addin, compile it, instrument it, and then delay sign it at the end of the build process, but I was hoping to avoid those kinds of hijinks with the project files.