Expert Texture Home Contact me About Subscribe Digipede Connect on LinkedIn rwandering on Twitter rwandering on FriendFeed

rwandering.net

The blogged wandering of Robert W. Anderson

COM APIs for .NET Libraries

Recently I added a COM API to the Digipede Framework API – developing a good, maintainable COM API was critical. The “easy” Microsoft .NET COM interop works pretty well, but it defaults too many things for those of us building public libraries.

If your public library needs to support COM, there are several steps you will want to take to make your COM API easier to maintain and to allow your library to behave (or appear) as COM clients expect.

I am thinking of writing an article (or a series of blog entries) on the steps I took designing our COM API. While some material exists out there on this (most of it pure reference), none of it brings it all together, soup to nuts.

My quick outline for the article:

  1. Introduction
  2. Limitations of COM interfaces
  3. Overriding the class interface
  4. Eventing interfaces
  5. Building your Type Library
  6. Embedding your Type Library
  7. Enabling Registration-Free COM
  8. Building a COM API Reference w/NDoc

Every section will include examples.

I guess my only question is: do I blog it or write an article for one of the many .NET related sites? If I write an article, which site should I submit it to?

Tags: ,

    Trackback

No comments yet »

Your comment

HTML-Tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>