---
title: "Continued COM interop discussion"
url: "https://osherove.com/blog/2003/2/10/continued-com-interop-discussion.md"
canonical: "https://osherove.com/blog/2003/2/10/continued-com-interop-discussion.html"
published: "2003-02-10T11:12:00"
updated: "2003-02-10T11:12:00"
tags: []
author: "Roy Osherove"
description: "In reply to my rants about COM Interop , Sam Gentile writes: No, it shouldn't but it is . Welcome to the sometimes nightmare known as COM Interop. I have written extensively on this area starting about a year ago…"
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# Continued COM interop discussion

By Roy Osherove February 10, 2003

**Historical article** · Originally published February 10, 2003; technical details may be outdated.

**In reply to my [rants about COM Interop](http://dotnetweblogs.com/ROsehrove/archive/02102003.aspx#2120), [Sam Gentile](http://dotnetweblogs.com/sgentile) writes:**

_**No, it shouldn't but it is**. Welcome to the sometimes nightmare known as_ [_COM Interop._](http://dotnetweblogs.com/sgentile/Story/362.aspx) _I have written extensively on this area starting about a year ago thinking the whole darn_ [_thing was flawed_](http://dotnetweblogs.com/sgentile/Story/1987.aspx) _evolving to a_ [_state of acceptance_](http://dotnetweblogs.com/sgentile/Story/294.aspx) _that its the best that could be done. Check them out._

I just did. it's nice to get the feeling that you are not the only one who feels a bit helpless at the sight of these COM interop flaws and misleadings. I do wonder whether there are any news from MSFT about revising/changin this whole approach in the upcoming versions... surly this can't go on.

I think a lot of developers and shops that bought into this whole interop being "easy" will try, burn and maybe even go back to their old VB/Other COM apps, since rwriting their whole structure would just be too much to handle in one big swoop.


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/