Thinking of building an add-in for Outlook 2003 with Visual Studio 2005? Don’t do it. Really, don’t do it. What? Ok, if you must… I’ve just spend the last three days building an add-in and installing on on a single PC. This totaled about 3 hours of development time and the rest was getting the darn thing to load! Honestly, it was the single most frustrating thing I’ve ever encountered in years. The problem was that the setup program that Visual Studio 2005 automatically generates when you create an add-in project doesn’t include everything you need. Here is how I fixed the problem: Before you can load your add-in you need to make sure the following is installed:
- Visual Studio 2005 Tools for Office Second Edition Runtime (found at http://shrinkster.com/mnh)
- Office 2003 Update: Redistributable Primary Interop Assemblies (found at http://shrinkster.com/mni)
After that you’ll need to “fully trust” your assemblies. This can only be done with signed assemblies. I remember being a pain with VS 2003 but turns out is a breeze with VS 2005. Just open up the Properties for the project and select the Signing tab. From there is was fairly self explanatory. Now comes the part that gave me problems. After you have everything installed (including your nice newly signed assemblies) you need to give permission to those assemblies. This is done using a tool called CASPOL.EXE. Here is the command line for registering your file:
caspol -u -ag All_Code -url "<full path to your file>" FullTrust -n "<assembly name>"
If you have more than one file (or the above didn’t work) you can also do this for a directory.
caspol -u -ag All_Code -url "<directory path>*" FullTrust
I hope this helps save someone from the pain I experienced over the last few days. Hopefully this will get easier with the next release of Visual Studio… Updated to reference Outlook 2003. I wasn’t clear about that in the original post.