Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Technically, you're not implementing the interfaces in C++ but MIDL. It's a separate interface language and it's worth knowing if you're going to do COM work.</p> <p>Anyway, it's not uncommon to use .NET interops to implement COM objects, but the two are not really compatible technologies. You WILL run into gotchas unless you're writing very simple objects.</p> <p>To get you started, here's some random assortment of pointers along with a couple of articles that I've used in the past.</p> <ul> <li>COM is an interface-driven technology. Repeat that to yourself again and again.</li> <li>Develop the interface definition separately, using MIDL.</li> <li>COM garbage collection is deterministic (reference counting), but this starts to fall apart when used with .NET, where the garbage collection happens automatically and unpredictably.</li> <li>Dealing with Eventsinks/event handlers is ugly.</li> </ul> <p>A small taste of the type of headaches you'll run into: <a href="http://www.codeproject.com/KB/cs/LingeringCOMObjects.aspx" rel="nofollow noreferrer">http://www.codeproject.com/KB/cs/LingeringCOMObjects.aspx</a></p> <p>More on why you should NOT let Visual Studio auto-generate the COM interface for you: <a href="http://blogs.msdn.com/mbend/archive/2007/04/17/classinterfacetype-none-is-my-recommended-option-over-autodispatch-autodual.aspx" rel="nofollow noreferrer">http://blogs.msdn.com/mbend/archive/2007/04/17/classinterfacetype-none-is-my-recommended-option-over-autodispatch-autodual.aspx</a></p> <p>Bridging events: <a href="http://www.west-wind.com/presentations/dotnetfromVfp/DotNetFromVfp_EventHandling.asp" rel="nofollow noreferrer">http://www.west-wind.com/presentations/dotnetfromVfp/DotNetFromVfp_EventHandling.asp</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload