I wrote about a few debugging
tips for VSTO the other day. Something else just came up this morning that I
should add. Does this scenario sound familiar?
Well guess what? You just broke a fundamental rule of the
CLR -- the "assembly name" (the thing you pass to Assembly.Load)
must match the internal "assembly name" (the thing inside the Manifest).
The compiler sets the Manifest's name to be the same as the DLL's name when you
build the project, and manually re-naming the DLL after the fact will cause
You have to go to the Project Properties inside VS, change
the output name to MyCoolTemplate.dll,
and then re-build the project. (This should also fix up the custom properties
This "bug" came up several times during the
product cycle, and it just came up again today. If it ever comes up again, I'll
have a URL to point to ;-)