I have create a c# application with a windows service and 2 vsto projects. Once the MSI has been created/installed i can see the one add-in was installed and the service is deployed as well. My problem comes in where only one of the vsto projects is installed. The one that is giving me nightmares is a Outlook visual designer ribbon. The other vsto project is a non visual add-in, and that one installs just fine. For the life of me i can't figure out why the visual designer is not installing, it is not in outlook options and not in control panel/add remove either. Compiling it from Visual studio everything works fine and runs as it should. Does anyone maybe have an idea of what could be wrong? Thanks in advance.
If you don't see your add-in listed on the COM add-ins dialog the required windows registry keys were not added properly. See Registry Entries for Application-Level Add-Ins for more information.
Make sure that you did all the necessary steps described in the Deploying an Office Solution by Using Windows Installer article.
Related
I have a vsto add-in for outlook developed in Visual Studio 2010 (.NET 4.0), but now when I tried to add this add-in for Outlook 2016 it is showing invalid vsto add-in. My question is:
Can the VSTO solution developed in Visual Studio 2010/12 support in Outlook 2016?
If not then what's the alternate or if yes then what I am doing wrong here?
A VSTO add-in should be installed on the machine. At least you need to add the required windows registry entries to load the add-in, you can't just add it. See Registry Entries for Application-Level Add-Ins and Registry Entries for VSTO Add-ins for more information.
My question is 'Can the vsto solution developed in Visual Studio 2010/12 support in Outlook 2016?'
Yes, it can. See Running Solutions in Different Versions of Microsoft Office. It states the following:
Microsoft Office applications can also run solutions created by using previous versions of Visual Studio. In some cases, these solutions require different versions of the Visual Studio Tools for Office runtime. Different versions of the Visual Studio Tools for Office runtime can be installed side-by-side on the same computer.
I'd suggest creating an installer which can check for preprequsites if any, add the required windows registry keys and install the plug-in on the system.
You may find the following articles helpful:
Deploying an Office Solution by Using Windows Installer
Deploying an Office Solution by Using ClickOnce
I have developed one add-in using Outlook 2010 AddIn for outlook 2013 with visual studio 2012. I have developed User Controls and worked with Custom Task Pane in Add In.
It works perfectly when I debug add-in from visual studio. I have created setup file using Install Shield Limited Edition (following basic steps given by forum). However, if I install that add-in and open Outlook, Add In does not load and is not visible on Home tab. Nothing happen.
I haven't made any registry entry while building setup file.
Please let me know how can i make it working.
Thanks.
You will have to make an entry to Registry. You can simply do through Install shield program.
Here is the quick screen shot:
Make sure that the loadBehaviour is set to 3.
If there is any error in the addon on load then it will set to back to 0.
It has been long time I did not developed the addon but I am sure my information is correct.
Also make sure that the you look after for 64 vs 32 bits entry.
I found a quick link for you too: http://blogs.msdn.com/b/emeamsgdev/archive/2013/11/21/outlook-deploying-an-outlook-2013-add-in-using-installshield-le.aspx
I've written an Outlook add-in for our office that I'd like to make available to others for testing.
My Googling has indicated that I should make an InstallShield project in the solution and use that, however my Visual Studio install only opens an InstallShield download page for which there is a dead link.
Following this failure, I attempted to manually add the add-in to Outlook by utilizing the files in the bin directory, but it tells me that it is an invalid add-in.
I'm at a bit of a loss here on how to proceed in making this add-in available for distribution.
You could use click-once, right click the outlook project in solution explorer and select publish and follow the wizard. The only problem would be that you will need to sign the click-once app because office addins are particular about security.
This question has further details.
I have developed a Outlook Addin using VSTO in Visual Studio 2010, on Windows XP/SP 3.
Build the VSTO solution, and I open Outlook 2010.
I see that the Add in has been installed. ( which is strange ).
Shut down Outlook.
Clean the VSTO solution 5) Open Outlook 2010, the add in is not
there.
So I believe Outlook understands that an Outlook add in is there, but I dont want the mentioned behaviour.
What am I looking for :-
I have created the installer using ClickOnce .
I should only see the Outlook addin , once I have executed the installer.
Any ideas shall be helpful.
When you build a VSTO addin, it gets automatically installed on your development machine. It is Visual Studio that is doing this for you, to make debugging easyer.
You can probably uninstall your addin automatically by using post-build events, but "Clean project" may be just as easy.
I have one shared add-in created in visual Studio 2005. This Add-in is worked on my system fine but if i tried to run this add-in on different system then it is not working. I found the problem behinde this but is it correct or not.
In my view the problem is when we create add-in through visual studio then the entry of this add-in is internally done by visual studio in registray file, so if we can try to run add-in created on particular system,to different system then this is not working because of this.
my process to run this add-in on different system is
copy my add-in project to different system and then build this project and tried to run add-in but its not working.
so is there any solution for this??
Create a Setup and Deployment type project for your add-in. The resulting installer will create the Registry entries needed to run your add-in.
The required Registry entries for Office add-ins are described here:
Registry Entries for Application-Level Add-Ins