3 Comments

VSTO Addins break after Visual Studio 2010 SP1 install, can't find config file

I ran into a breaking change with Visual Studio 2010 SP1 and VSTO at a client today. It seems there was a change that caused Office addins to look for their config files in the application’s folder instead of from the addin’s folder (e.g. Word.exe.config or Excel.exe.config). The result is all sorts of chaos with AppSettings, WCF service bindings and anything else that needs to be read from the app.config

The details are posted here on connect - Visual Studio SP1 (or specifically VSTO sp1) Issue with config file location

The bug was caused by a change in the way VSTO 4.0 SP1 reads the Manifest value in the Windows Registry. Previously “[TARGETDIR]MyWordAddIn.vsto|vstolocal“ was valid but the URI has changed in SP1

Registrykeys

3 Comments

2 Comments

The case of the Missing Team Project in VS 2010

Ran into a strange issue today when trying to upgrade a project from VS2008 to VS2010. We are running TFS 2010 and the Team Project appears fine in Team Explorer under VS2008 but is mysteriously missing from Team Explorer in VS2010. My windows account is also part of the Project Collection Administrators group.

SNAGHTML3fab60

SNAGHTML3c486f

2 Comments

Comment

VSTO Tip - Show Errors from your Add-In

By default, Microsoft have chosen to hide user interface errors for Office add-ins. That means whenever an unhandled exception occurs, you are none the wiser if you’re not debugging. There are two solutions to this:

  1. Implement an exception handler (like LadyLog)
  2. Show the errors by changing the end user options

Comment