The Visual Studio setup project created when you create a COM add-in using the Shared Add-In Wizard provides a setup package that you can use to deploy your COM add-in to your customers' machines. At first glance, the setup created by Visual Studio appears to cover all the deployment requirements for COM add-ins, but alas life is not quite that easy. A deployed COM add-in written in managed code really needs to be "shimmed." To understand what a shim is and why it is needed, we have to dig into how a COM add-in written in managed code is actually loaded into an Office application.
Part One. An Introduction to VSTO
An Introduction to Office Programming
Introduction to Office Solutions
Part Two. Office Programming in .NET
Programming Excel
Working with Excel Events
Working with Excel Objects
Programming Word
Working with Word Events
Working with Word Objects
Programming Outlook
Working with Outlook Events
Working with Outlook Objects
Introduction to InfoPath
Part Three. Office Programming in VSTO
The VSTO Programming Model
Using Windows Forms in VSTO
Working with Actions Pane
Working with Smart Tags in VSTO
VSTO Data Programming
Server Data Scenarios
.NET Code Security
Deployment
Part Four. Advanced Office Programming
Working with XML in Excel
Working with XML in Word
Developing COM Add-Ins for Word and Excel
Creating Outlook Add-Ins with VSTO