Hi all



We have a 3-Tier Architecture that uses com+ from the days when our
websites used just classic ASP. All the .net examples I have found are
not using com+ or Enterprise Services. As I would like to revisit
this, to see if we should be still using com+ in our 3-Tier
Architecture but am unable to find documentation as to when to use com
+ and when not.



Does anybody know of any?



Or anybody have any thoughts this ?



Many thanks

Paul

Hello (E-Mail Removed),

COM+ is used widely by the windows, and it's not disappeared.
Everything depends on that are you gonna do.
If your are only concerning about rewriting the COM+ i think it's not very
good idea if it works very well right now.

So, if you have no problems with it - keep it as is.

If your are want to do with it by any means, i'd recomment to wrap it into
the EnterpriseServices. ES it the .NET wrapper upon COM+, exposing the number
interfaces with is used the COM+ beneath.

The only problem is that if you want to expose your com+ to outside of your
environment, for exaple using in internet, your com+ needs to be wrapped
by webservices (either introducing WCF or just providing SOAP by standard
way for EnterpriseServices)

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

> Hi all
>
> We have a 3-Tier Architecture that uses com+ from the days when our
> websites used just classic ASP. All the .net examples I have found are
> not using com+ or Enterprise Services. As I would like to revisit
> this, to see if we should be still using com+ in our 3-Tier
> Architecture but am unable to find documentation as to when to use com
> + and when not.
>
> Does anybody know of any?
>
> Or anybody have any thoughts this ?
>
> Many thanks
>
> Paul
>