Advantages of COM+
Can have a distributed transaction over more then one database
Don't need to pass around the connection/transaction
Disadvantages of COM+
Have to have strong named assemblies - not optional
Can't use any non-strong named assemblies in your project
Easy wind up with some sort of configuration/versioning problem
Personally, I would avoid COM+ whenever possible. It is not that much effort
to have a central place to store your transaction related objects, so all
your code can use it. It really comes down to how many databases are
involved. If just 1, I would go for just ADO transaction, if more then 1,
you have no choice but to go with COM+
"Mythran" <ki********@hotmail.comREMOVETRAIL> wrote in message
news:eg**************@TK2MSFTNGP09.phx.gbl...
I just want to know the advantages vs disadvantages of using Component
Services to handle our web application transactions over creating and
passing around a transaction object of our own? When would you use one
over the other, or use one instead of the other?
Thanks :)
Mythran