N-tier applications with VB.NET: Where to put everything practically?

D

DraguVaso

Hi,

I'm developping VB.NET-applications for 2 years now, and I'm now moving on
to bigger porjects, so I'm examining the use of Visio for enterprise
architects, and 'the design' we should use.

I'm my whole carreer already using the concept of the 3 tiers
(presentation-, business- and datalayer), but I don't now 'the exact way' to
do it (shame on me, hehe). Does anybody know some good articles about this
subject? So not the theoretical way, but really more practical.

What do I have to put actually in which layer? Les't take for exemple a
simple application that let the user administer the Northwind-database.
- Do I create one big Datalayer-class with different SqlDataAdapters and 1
DataSet? Or one class with one SqlDataAdapter and its own DataSet that I
inherit for every object/table?
- The logic behind for exemple a "Save"-button on a Form with a DataGrid: Do
I put this in the Business Layer, or in the Presentation Layer?
- The same with for exemple a button that will open a Form that shows all
the Orders of a Customer? Where do I search for its Orders etc?
- Do I create for each Form its own Business-class?

I know I'm asking some really dumb questions, but I'm getting confused, and
I really want to know the 'right' way :)

Thanks a lot for any hints, documents, example
 
D

David Young

There's a good article at the Patterns and Practices website called
"Application Architecture of .Net: Designing Applications and Services".
Its a real good read. It leans heavily in the SOA direction, as do most of
their papers these days, so you'll have to look past that (unless you need
that functionality).
http://www.microsoft.com/resources/practices/default.mspx

Dave
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top