how do I get my vsto to work on Excel without the settings of Visual Studio? im trying to add not valid. can you help me a solution for that
the file that I have
If you are trying to distribute a VSTO add-in, the target machines will need the VSTO runtime.
https://www.microsoft.com/en-us/download/details.aspx?id=48217
Related
I have a c# COM Add-in developed for Outlook that was created years ago in Visual Studio 2010. It was installed on a computer using Office 2010 and works fine. We are now migrating to Office 365. I installed the Add-in and in Outlook's "File".."Options".."Add-ins" it is listed under the "Inactive Application Add-ins". When I click on the Go button under the "Manage" - "COM Add-ins", the add-in is listed but not checked. When I check it, it shows "Load Behavior: Not loaded. A runtime error occurred during the loading of the COM Add-in." The old Add-in was compiled as 32 bit and I tried to install it as that, then recompiled it as a 64 bit app and installed that but it gives me the same message. Should COM Add-ins work in Office/Outlook 365? Is there something that needs to be updated?
Should COM Add-ins work in Office/Outlook 365?
Yes, they should work correctly. There were no breaking changes.
Microsoft Office applications can disable VSTO Add-ins that behave unexpectedly. If an application does not load your VSTO Add-in, the application might have hard disabled or soft disabled your VSTO Add-in.
Hard disabling can occur when a VSTO 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 VSTO Add-in is executing.
Soft disabling can occur when a VSTO Add-in produces an error that does not cause the application to unexpectedly close. For example, an application might soft disable a VSTO Add-in if it throws an unhandled exception while the Startup event handler is executing.
When you re-enable a soft-disabled VSTO Add-in, the application immediately attempts to load the VSTO Add-in. If the problem that initially caused the application to soft disable the VSTO Add-in has not been fixed, the application will soft disable the VSTO Add-in again.
Is there something that needs to be updated?
You need to check add-in prerequisites, make sure that all of them were installed correctly. Then try to log all startup operations and see where an exception is thrown.
If you use VSTO, make sure that you did all the steps described in the Deploy an Office solution by using Windows Installer article.
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´ve created several VSTO add-ins for Outlook/Word/Excel/PowerPoint.
When i build them & then start the accociated program, the add-ins are installed and work wonderful.
When I try to install the DLL manually, in "Options > Add-Ins > COM-Add-Ins:Go to... > Add..." and then select the DLL, the program tells me, that it is not a valid Add-In.
What is the problem here? Visual Studio 2010 can install them automatically.
Can someone help me?
Thanks!
The simplest way to make an installer for your add-ins is to use the "Publish" functionality. Right click your Add-in project and select publish. This will show a wizard with basic options. This will generate an EXE file and a series of other files that are needed to install in other machines.
A .net VSTO addin DLL is not a normal COM dll (for instance, it doesn't self register, it has no TLB embedded within it) so Word can't deal with it through that addin's dialog as far as I know. VSTO addin's have to be installed via an installer.
I have created an Outlook addin using VS2010 and VSTO 4.0.
On Windows7+Outlook 2010, the installation and and application behaves as expected.
On Vista+Outlook 2007 (fresh installed virtual machine), the installer complains that it does not recognize the .vsto file format.
Has anyone experienced this? When I previously created VSTO3.0 addins and used them on Outlook 2007 I had no problems with installation.
You need to install the VSTO 4.0 runtime (which comes pre-installed with 2010, but not with 2007). You can download it from Microsoft right here.
If you deploy using ClickOnce this runtime gets added to the prerequisites automatically.