Hello Dave,
I reviewed the whole thread. Based on my understanding, currently you are
using Shim to create addins for Office XP. However, you are not sure of the
internal things in how Shim works. So you have questions on registry keys,
dependency DLLs, and etc. Right?
To answer this question, I think we first need to go through why we need
shim under this situation. Deploying and installing a managed COM add-in
securely in Microsoft Office XP currently requires the assembly be hosted
in an unmanaged COM add-in proxy component called a shim. For what a shim
is and why it is currently needed to deploy COM add-in DLLs, this KB aricle
is quite useful:
"Deployment of Managed COM Add-Ins in Office XP"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoxpta/htm
l/odc_ofshim.asp
(I know you have read it. But I still paste it here, maybe some other
community member can benefit from it.

)
OK, then let's continue on this topic.
VS.NET installer is a powerful tool, which will do most of things for you
and bring you convenience. However, as a coin has two sides, using it may
hide some internal things from developers so sometimes we may feel confused
on the errors.
In order to dig into it, we may need to check into that ATL shim project.
As Peter mentioned, the rgs file contains info that shim ATL project writes
to registry. Also, that ATL project does some thing such as regsvr32 so
that when runnning it, the shim will be registered automatically.
When deploying this type of solution, it is important to keep in mind that
all assemblies and the shim DLL need to be placed in the same directory on
the target machine. Then the shim needs to be self-registered using
regsvr32. I think that is the main work that VS.NET installer project does.
Also, you can refer to this step by step sample for more details:
"Using the COM Add-in Shim Solution to Deploy Managed COM Add-ins in Office
XP"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoxpta/htm
l/odc_comshim.asp
Unfortunately, there is no public document on how to do it step by step
like a install script. So we may still need to dig into project code, and
some materials for the internal info. Troubleshooting is a time consuming
work. But please feel free to post here or contact Microsoft PSS when you
need assistance from us. We are glad to be of assistance.
Thanks very much for your understanding.
Best regards,
Yanhong Huang
Microsoft Community Support
Get Secure! ¨C
www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
-http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.as
p&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.