Hi
In my application architecture, the business logic classes talk to the
data access classes. The business logic classes might also talk to other
business logic classes. The business logic classes are not aware of
handling transactions, handling connection etc. They are done by data
access classes.
Eg.,
The code in a typical business logic class looks like this.
Public Function CreateEmployee()
Dim oEmpDL as new EmpDL
EmpID = oEmpDL.InsertEmployee(employee object)
Dim oAddress as new AddressDL
oAddress.InsertAddress(EmpID, Addressobject)
End Function
The InsertEmployee and InsertAddress methods open and close the
connection. The problem with this appproach is handling transactions. I
cannot use ADO.Net transactions. One way is to use COM+ transactions and
inherit the data access components from ServicedComponnet class. But
this has some overhead of having strong names and registering the dlls
in com+ services.
I came across an article on ServiceConfig class
(http://www.15seconds.com/issue/030930.htm) which provides COM+ services
without the need of registering dlls. I could not see more information
on this class on MSDN. Is there any draw back on using this. Has anybody
used this on a production environment? My another requirement is data
will be in multiple databases and hence there is a need for distributed
transaction. Any help/suggestion is appreciated.
Thanks
rjn
*** Sent via Developersdex http://www.developersdex.com ***
