Office 2010 VSTO AddIn Not Loading

Possible duplicate:
Troubleshoot adding VSTO that doesn't load?

I have an Outlook add-in for VSTO 2010 Office 2010. It works with installation on my development computer and on a standard user machine and does not work with another. When I run the look, it says that a runtime error occurred while loading the runtime add. If I go to the addin installation directory and manually run the VSTO deployment manifest file, it will come with the Office Setup installation wizard and install the add-in in order, then we will start Outlook and it will work. Any ideas guys ?!

I have completed the following prerequisites:

  • .NET 4 / Client Profile
  • Visual stuio 2010 office tools
  • Office 2010!
  • office 2010 PIAs
  • My add-in
  • Reg key to download VSTO, pointign ti install vsto and | vstolocal
  • Installed in program files, so no inclusion list required
  • FUll permission manager on the machine

THANKS!

+4
source share
2 answers

Are you checking your VSTO log file? This can be done by adding the following system environment variables:

NAME: VSTO_LOGALERTS VALUE: 1 

There may be an exception error, so your add-in does not load.

You can check this source for more information on logging and VSTO alerts, but essentially you change two values โ€‹โ€‹of the environment variables depending on what you need to do:

Display VSTO alert hints

To display each error in the message box, set the VSTO_SUPPRESSDISPLAYALERTS variable to 0 (zero). You can suppress messages by setting the variable to 1 (one).

Logging VSTO alerts in a log file

To write errors to the log file, set the VSTO_LOGALERTS variable to 1 (one).

Visual Studio Tools for Office creates a log file in the folder that contains the application manifest. The default name is.manifest.log. To stop registration errors, set the variable to 0 (zero).

+4
source

One thing to check is whether the problem machine is running a 64-bit or 32-bit version of Office. I do not mean the computer itself (your AddIn can happily support a combination of 32-bit and 64-bit machines), I mean Office software.

We were stuck as you tried to understand why our admin worked on some machines and not on others, and in the end it turned out that the problem with 32-bit versions of 64-bit versions of Office turned out to be a problem in itself.

The solution was to force all users to use the same 32-bit version of Office.

+2
source

Source: https://habr.com/ru/post/1337584/


All Articles