I'm using Win2003 server .Net 1.1 and migrating from a ServicedComponent
dervived data access layer to "services without components". I've seen some
simple examples, but nothing that really clarifies the following for a real
enterprise solution:

- lets say business logic initiates a transaction by entering code in a new
ServiceDomain with transaction required. It then creates and uses several
data access layer objects. Does each data access layer object method have to
create its own ServiceDomain or will it automatically be part of the callers
ServiceDomain ?

- is SetAbort/SetComplete on ContextUtil even required ? Is it required for
each DAL method I execute within the ServiceDomain ? This is where I have
seen no similar usage. Some examples just throw exceptions and never call
SetAbort/SetComplete, and some do it in every call in the chain. Actually
most examples don't even make calls outside of the initiating class, so hard
to say.

this seems like a great feature, but I don't have a ton of time for trial
and error to figure out the transaction coding model.

thanks!