We have created a outlook Module extension Add-in. it works in outlook 2016 onward as per following link https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/extension-module-outlook-add-ins . We want to submit this add-in in office store. We have submit it to the office store but store rejects the Add-in on below grounds-
The add-in does not appear on Outlook 2013.
The add-in does not appear on Outlook 2016 for Mac.
The add-in does not appear on Outlook 2016 on Chrome browser.
The add-in does not appear on Outlook on Safari browser (Version: 13.1 15609.1.20.111.8)).
Add-in can't be work inside these environment since Module extensions are only supported by Outlook 2016 or later on Windows.
Can somebody help me how i can submit my module add-in which can pass these features?
Related
I have a COM add-in for Outlook desktop and it is missing from my ribbon. Yet, I see the registry key is present. Do you have any suggestions on how I can get the add-in to appear?
I am using Outlook 2013 application to test the Outlook add-in I am creating. At the moment, when I click a button on my add-in, it is just saying App Error and I don't know what is causing it.
Is there a way for me to debug my code to see where the error is coming from?
I depends on your windows version, have a look here.
For Windows 10:
Launch the F12 development tools that corresponds to your version of Office:
For the 32-bit version of Office, use C:\Windows\System32\F12\IEChooser.exe
For the 64-bit version of Office, use C:\Windows\SysWOW64\F12\IEChooser.exe
Whenever I build the Add-in from Visual studio(2017 Community version),the add-in gets loaded in Outlook(2016) and functions as expected.But when I remove the add-in from Outlook and then try to install it using the .msi installer file the add-in doesn't gets loaded in the Outlook.
Anyone having any idea about this?
I am trying to build a simple addin for Word 2007 using Visual Studio 2010 and .NET 4.0. It's a relatively simple addin, which brings up a save dialog and saves the document as a Word 2003 document.
The addin runs fine in Word under Debug mode, but does not run under Release or when I create a setup project for it. (It does create the registry keys under HKCU\Software\Microsoft\Office\Word\Addins and they look to be correct) I don't get any errors, and the addin isn't listed under the Disabled Addins either.
I tried adding the Addin manually but it says that it isn't a valid addin. The version of Office is 32-bit, running under Windows 7 64-bit.
Or are there even any alternatives to using VSTO (VBA?) that will let me add a tab to the Ribbon?
You can use IRibbonExtensibility interface (http://msdn.microsoft.com/en-us/library/microsoft.office.core.iribbonextensibility.aspx) to avoid using VSTO.
I made an Outlook macro. How can I deploy it to use it on some other machine?
Do I follow the same steps I followed on my machine Tools-> Macros-> create new or is there another way to deploy as we do with the vb or C# projects?
No, you don't need to follow the same steps and re-record the entire macro from scratch. You can save the module containing the macro and import it in Outlook on the other machine.
In Outlook's VBA editor, right-click your module > Export File...
Then on the other machine, in Outlook's VBA editor, right-click your project > Import File...
EDIT You say that your Outlook doesn't have VB Editor. Quoting from Outlook help:
you may be running a Microsoft Office
program with the Visual Basic for
Applications (VBA) shared feature disabled.
I don't know what version of Outlook you have, but for 2003:
To re-enable VBA, follow these steps:
1.Run the Office Setup program again. How? Quit all programs.Double-click
the Add/Remove Programs icon in the
Microsoft Windows Control Panel.Do one
of the following: If you installed
your Office program as part of
Microsoft Office, click Microsoft
Office in the Currently installed
programs box, and then click the
Change button.If you installed your
Office program individually, click the
name of your program in the Currently
installed programs box, and then click
the Change button.
2.On the Features to install screen in the Setup program, click the plus sign
(+) next to Office Shared Features.
3.Select Visual Basic for Applications, click the arrow next to
your selection, and then click Run
from My Computer.
Usually outlook macros are only made for personnal use. Distributing them can be hard as it needs too much actions made by the user (add "devoloper" in ribbon, open visual basic editor, import files, enable references, enable security...).
Microsoft wrote:
If you are developing a solution that you intend to distribute to more than a few people, you should convert your VBA code into an Outlook COM or VSTO add-in or an Office add-in for Outlook.
(source: https://support.microsoft.com/en-us/help/290779/managing-and-distributing-outlook-visual-basic-for-vba).
Knowing that, i recommend you to write a VSTO add-in and deploy it using ClickOnce.
You can start by these links:
VSTO
https://learn.microsoft.com/en-us/visualstudio/vsto/getting-started-programming-vsto-add-ins?view=vs-2019
ClickOnce deployment
https://learn.microsoft.com/en-us/visualstudio/vsto/deploying-an-office-solution-by-using-clickonce?view=vs-2019