Hello Carlos and thank you.
In what I've done with add-ins so far I haven't noticed any need to map COM
objects to .Net objects (i.e. unmanaged to managed), even though I have
written the add-in code in managed C++. Can you elaborate on this?

Signature
Greg McPherran
www.McPherran.com
Hi Greg,
VS.NET is not a managed (.NET) app yet, so managed add-ins use Interop
assemblies internally. You don´t need to map anything, but the COM objects
are underlying there. In the past, despite programming a managed add-in (C#,
VB.NET) you had to register your add-in dll assembly for COM interop using
regasm.exe or equivalent, and you had to use an ActiveX shim control to host
.NET usercontrols in the toolwindows of your add-in. Despite this has been
eliminated, the .NET objects that you use in your managed assemblies are
wrappers around COM objects, and in fact you will see quite a few
COMExceptions from time to time.

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio 2005, Visual Studio .NET,
VB6, VB5 and VBA
You can code, design and document much faster in VB.NET, C#, C++ or VJ#
Free resources for add-in developers:
http://www.mztools.com
> Hello Carlos and thank you.
>
> In what I've done with add-ins so far I haven't noticed any need to map
> COM
> objects to .Net objects (i.e. unmanaged to managed), even though I have
> written the add-in code in managed C++. Can you elaborate on this?