This question is locked. New answers and comments are not allowed.
I have a web based application as following layser:
1.DataContext to hold context class and entity class
2.Service to handle all business logic
3.Web UI
My query is as below:
1.Whether it's neccessary to split the DataContext as two projects:Entity project and Context project?
2.Is there any risk if UI to call datacontext class for updating and inserting?
3.As my understanding, whether only service layer can call datacontext class and UI only call service? The entity is shared for all projects.
4.I see your links http://www.telerik.com/help/openaccess-orm/dev-guide-web-development-manage-context-overview.html. If I don't dispose the OpenAccessContext object, is there any risk?
5.For transaction, what's the advantage of OpenAccesORM than System Transaction?
1.DataContext to hold context class and entity class
2.Service to handle all business logic
3.Web UI
My query is as below:
1.Whether it's neccessary to split the DataContext as two projects:Entity project and Context project?
2.Is there any risk if UI to call datacontext class for updating and inserting?
3.As my understanding, whether only service layer can call datacontext class and UI only call service? The entity is shared for all projects.
4.I see your links http://www.telerik.com/help/openaccess-orm/dev-guide-web-development-manage-context-overview.html. If I don't dispose the OpenAccessContext object, is there any risk?
5.For transaction, what's the advantage of OpenAccesORM than System Transaction?