E
epigram
I'm creating a data-centric asp.net application that will be using SQL
Server 2000. I'm looking for some articles, design tips, etc. to help me
decide how I should design my application. I realize this is an obtuse
request, but I just want to follow some best practices. Most of the
examples I see have a micro focus on one particular aspect or another of
technologies used in an asp.net application.
If I simply aggragate all of those types of examples and take a brute force
approach to my application, I'd end up with a ton of code directly in my
code-behind files that connect to the db, perform business logic, etc. This
doesn't appear to be a good approach. I'd like to see a simple example of a
well designed asp.net app. In particular, I want to see a high level
architectual view that would show what logical and physical layers typically
exist (i.e. asp.net presentation layer, business objects layer, data layer).
I'd also then like to see a couple of concrete round-trip examples using
that architecture so I could see how the various layers interact.
Most of the architecture articles I have seen really revolve around
constructing highly decoupled, generic data layers. I know I will be using
SQL Server 2000, so those seem to be a little overkill for my purposes. I'm
not sure if it would be best to have a simple class that was only
responsible for connection pooling, leasing out data connections, etc. Or
is it a best practice in asp.net/ado.net to create object wrappers (i.e.
classes that encapsulate the logical schema for the db) and the architecture
to support those wrapper classes.
Any help would be much appreciated.
Thanks!
Server 2000. I'm looking for some articles, design tips, etc. to help me
decide how I should design my application. I realize this is an obtuse
request, but I just want to follow some best practices. Most of the
examples I see have a micro focus on one particular aspect or another of
technologies used in an asp.net application.
If I simply aggragate all of those types of examples and take a brute force
approach to my application, I'd end up with a ton of code directly in my
code-behind files that connect to the db, perform business logic, etc. This
doesn't appear to be a good approach. I'd like to see a simple example of a
well designed asp.net app. In particular, I want to see a high level
architectual view that would show what logical and physical layers typically
exist (i.e. asp.net presentation layer, business objects layer, data layer).
I'd also then like to see a couple of concrete round-trip examples using
that architecture so I could see how the various layers interact.
Most of the architecture articles I have seen really revolve around
constructing highly decoupled, generic data layers. I know I will be using
SQL Server 2000, so those seem to be a little overkill for my purposes. I'm
not sure if it would be best to have a simple class that was only
responsible for connection pooling, leasing out data connections, etc. Or
is it a best practice in asp.net/ado.net to create object wrappers (i.e.
classes that encapsulate the logical schema for the db) and the architecture
to support those wrapper classes.
Any help would be much appreciated.
Thanks!