Is it possible to create .msi installation file to load a modern outlook web add-in (not native) on your pc to avoid to ask the user to load the add-in manifest manually?
Office web add-ins are not designed for deploying using MSI. Possible deployment options are described in the Deploy and publish Office Add-ins article.
In a cloud deployment, to distribute your add-in to users in your organization by using the Microsoft 365 admin center. To distribute your add-in publicly to users you can publish it to the AppSource (add-ins' store).
Related
I need to deploy an add-in created in yeoman on the outlook desktop.
How could I do it without using the local host?
Could it be done with an installer?
Nope. You need to deploy the add-in (web app) on any web server and share the manifest file for sideloading (or just publish the add-in to the store).`
We're developing an Outlook addin that is specific and proprietary to our organisation. So we'd rather not put it on AppSource and we'd rather not put the addin source files (all the js,css etc) on a publicly accessible url even if we can keep the manifest file private.
Is there a way, through centralised admin and deployment, to distribute this Outlook addin to our staff, using Group policies, and still keep all the addin files privately hosted somewhere?
Yes, you can deploy an add-in by side-loading the add-in manifest xml file using Centralized deployment.
Yes, you can host add-in files privately but make sure the add-in host is accessible from your Outlook client.
If add-in is bound to work only when the user is connected to a particular network/VPN, it is good to educate the user that the add-in is unavailable outside the network boundary.
For on-premises and online environments that do not use the Azure AD identity service, you can deploy Outlook add-ins via the Exchange server.
Outlook add-in deployment requires Office 365, Exchange Online, or Exchange Server 2013 or later. Outlook 2013 or later.
To assign add-ins to tenants, you use the Exchange admin center to upload a manifest directly, either from a file or a URL, or add an add-in from AppSource. To assign add-ins to individual users, you must use Exchange PowerShell. For details, see Install or remove Outlook add-ins for your organization on TechNet.
Read more about possible ways in the Deploy and publish Office Add-ins article.
I am planning to develop a outlook add-in which will work with the desktop version of outlook 2010 and 2013.
Can i publish it on the online office store (https://store.office.com/) or is it that the store only allows submission of office 365 apps???
I tried looking at the store's documentation but it does not mention anything on the topic.
I have tried contacting Microsoft support but they seem to have no clue.
You can't publish COM add-ins to the Office store.
COM add-ins (like any other Windows desktop applications) can be published to the Windows store.
Office Store only accepts JS based addins. COM addins for the desktop versions of Outlook cannot be distributed though the store.
I have a Wix setup created for my windows form application and i have a server to publish it . Earlier projects were published using ClickOnce application. Can i do that with my Wix setup too where the setup created would be integrated with the clickonce application. The user will click on the url and it will download only the setup.exe and when clicked on it , it will install the application according to the setting done in wix. I dont even know if the question is correct.
You cannot do that.
"ClickOnce application is any Windows Presentation Foundation, Windows Forms, or console application published using ClickOnce technology. You can publish a ClickOnce application in three different ways: from a Web page, from a network file share, or from media such as a CD-ROM."
We have developed a Outlook Add-in and want to share the add-in over network and deploy on user machine who does not have Admin rights. what is the best way to share the VSTO files over network since sending as email attachment is blocked.
You can develop a per-user add-in and then create a ClickOnce installer and publish it on a network share instead. See Deploying an Office Solution by Using ClickOnce for more information