I tried to created ms office shared add-in through visual studio 2005, and also created successfully. But i want to know some more information. Please answer the following question if anyone knows.

1) This Add-in map the mscoree.dll, why its map like this? and why its not mapping mydll.dll?
2) I tried to convert mydll as addin dll by running the following command regsvr32 "mydll.dll" But its not working i got the error dllEntry Server point was not found. Why i got this type of error?
3) How Add-in communicate with office?

1) mscoree.dll is how COM communicates with your .Net assembly. It's called a CCW - COM Callable Wrapper. You use regasm to create this registry entry
2) As above, do not use regsvr32 on a .Net assembly. Use regasm to register it for COM interop. See http://msdn.microsoft.com/en-us/library/tzat5yw6%28VS.71%29.aspx for more details.
3) I have no idea really, I don't do a lot of COM automation. Perhaps this will help: http://msdn.microsoft.com/en-us/library/3295w01c%28VS.80%29.aspx

---

Collin Sauve

Office Add-Ins are COM objects, but COM component is not .NET component. They are the different animals at all. Actually there are RCW/CCW as the bridge between COM and .NET. When you write the above managed Add-In, this is a .NET component. We need to write the enough information to registry(All COM objects all require registry information for interfaces, where to load,etc). COM Interop writes the same information to make COM Runtime to load .NET component in this way.

---

Best regards,
Riquel
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

1) mscoree.dll is how COM communicates with your .Net assembly. It's called a CCW - COM Callable Wrapper. You use regasm to create this registry entry
2) As above, do not use regsvr32 on a .Net assembly. Use regasm to register it for COM interop. See http://msdn.microsoft.com/en-us/library/tzat5yw6%28VS.71%29.aspx for more details.
3) I have no idea really, I don't do a lot of COM automation. Perhaps this will help: http://msdn.microsoft.com/en-us/library/3295w01c%28VS.80%29.aspx

---

Collin Sauve

Office Add-Ins are COM objects, but COM component is not .NET component. They are the different animals at all. Actually there are RCW/CCW as the bridge between COM and .NET. When you write the above managed Add-In, this is a .NET component. We need to write the enough information to registry(All COM objects all require registry information for interfaces, where to load,etc). COM Interop writes the same information to make COM Runtime to load .NET component in this way.

---

Best regards,
Riquel
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.