>Unfortunately your scenario is not uncommon at all. I've seen a lot of this recently and frankly this is the worst kind of FUDD you can throw at a development situation.
>

I've heard this several times now, so I wondered if .NET is intended to replace COM completely for the developer. I can see it possibly replacing COM for ActiveX, multi-language projects, and Web Services. Is there a mechanism in .NET to replace COM for Automation? Also, if you want to split up processes among several computers on the server side, wouldn't COM+ be a better choice? Or should we expect that all components will "evolve" to Web Services? Personally, I don't think I would want to expose everything, and I could probably do without the extra overhead of Web Services and IIS where they are not needed. What's your take on this?

Thanks.