Using COM+ services

Mahesh Chand

I have an internal debate going on here about using COM+ services in .NET (System.EnterpriseServices). Is any of you using these in their real projects? Are they worth using? It's not like I hate them, its like "NOT .NET". In my understanding, going without COM+ services is a better apparoach from the complexity and design perspective. Both approaches (using or not using) have their trade-offs. I know developers who come from COM/COM+ background want to enforce these as their "known standard" but is it really worth? Why do I make my object that complex so I can't live without using COM+ services. On the other hand I can break down my complex object into non-complex objects. Please discuss.

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

madinewala23y ago
Hi Mahesh, First of all, I shall thank you for running the above said chit chat... well, currently I'm into a real project, and I have windows 2000 OS available. Initially after going through enough of documentation on COM+ in .NET, I came to know that I could easily make my COM+ app. run as a windows service, but only on XP, 2003 and above OSs. Since I have Win2K, I decided of having all my business logic onto COM+, and the other required logic onto a Windows Service... Mahesh, I shall be grateful to you if you gimme me an idea of running the COM+ as a windows service on windows 2000 OS. But I feel very much comfortable using the COM+ in .NET. Its pretty easy in .NET, but one could see the features of it on the latest OSs - XP, Windows 2003... thanks, irfan
+1
chrishornberger23y ago
I've had little need to invoke anything outside of native .net stuff and stuff I've written myself. I haven't done any piece-meal project, but ground up each time. So... nope, haven't done it and haven't had a compelling reason to go out of my way to do it, either.
+1
Mahesh Chand23y ago
guys? YES/NO?
+1