Is this design ok?
In App_Code, i have the DBML folder and a AllClass folder. In AllClass folder i have my whateverclass.cs
In aspx.cs code behind, I instantiate the whateverclass.cs and call it's public method which calls the DBML or stored proc.
All my methods in whateverclass.cs are public. I have Update, Select and Insert methods, call stored proc. All the database
calls.
Is this a good way of coding this..is this not truly an object oriented design...it's like a one-on-one relationship with the database. Page calls database, pulls info, saves, updates, etc.
When I look at the code, i dont have reusable code. I have a class that logs user action. This should be ok, no? (I don't have
an architect on this app)
In aspx.cs code behind, I instantiate the whateverclass.cs and call it's public method which calls the DBML or stored proc.
All my methods in whateverclass.cs are public. I have Update, Select and Insert methods, call stored proc. All the database
calls.
Is this a good way of coding this..is this not truly an object oriented design...it's like a one-on-one relationship with the database. Page calls database, pulls info, saves, updates, etc.
When I look at the code, i dont have reusable code. I have a class that logs user action. This should be ok, no? (I don't have
an architect on this app)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
exactly.
so that it will be proper three tier architecture.
ASKER