question

[z f]

i use enterprise services for having transaction management.

i use one transactional component that is creating an ado.net connection,
and i pass this connection to not enterprise services components to use and
have transaction control in a central place in the project.
i can commit or rollback the operations from outside those objects.
as i tested this works.
i need to work this way since my programming model requires the use of
friend properties/methods that are not supported by enterprise services.
is there some reason why not to work this way?

TIA!

 

[S.M. Altaf [MVP]]

I didn't understand your question very well, but you just mentioned that you need to work this way, so I don't see why not!

-Altaf




--------------------------------------------------------------------------------
All that glitters has a high refractive index.
www.mendhak.com
i use enterprise services for having transaction management.

i use one transactional component that is creating an ado.net connection,
and i pass this connection to not enterprise services components to use and
have transaction control in a central place in the project.
i can commit or rollback the operations from outside those objects.
as i tested this works.
i need to work this way since my programming model requires the use of
friend properties/methods that are not supported by enterprise services.
is there some reason why not to work this way?

TIA!