Separating Business Logic - where to start?

[Sheedejef]

I'm used to the spagetti type code of classic ASP and want to learn more about separating out business logic to components in ASP.Net. Now, I've flipped through a few ASP.Net books and they all seem to gloss over this subject in a couple of pages. Can someone point me to good online articles or books that talk specifically about how to design a logical ASP.Net application? I'm confused about the differences between Components, Classes and Modules - when to use them, what their differences are, etc. Thanks.Components,and Module are classes as well, but usually componetns refer to classes that handle the business logic and Module are classes that are presenting the GUI like .aspx and ascx classes.<BR>business logic layer is a class library componenet that does the delete, add, update, get data function from the database and you call this class library component methods to do the interaction with the database for you.<BR><BR>one of the best online sources to explain this is the IBuySpy portal documentation.<BR>good luck