asp.net Application Design Help

[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!

[Elton Wang]

asp.net Application Design Help

Please take look at

http://msdn.microsoft.com/library/default.asp?

url=/library/en-us/dnbda/html/daag.asp

Hope it's helpful to you.

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