What I do is:
1) .aspx pages & Codebehind files(presentation layer) (a dll)
2) Business lLayer (logic cs files) (another dll)
3) Data Access Layer (a dll or web service or remoting)
Eva
Karthik Nataraaj <[EMAIL PROTECTED]> wrote:
hello,
I'm a bit new to n-tier architecture in asp.net. Normally I build
applications with a base class which contains the common functions
which is inherited in most of the code-behind files.
And I use a seperate DataAccess.cs namespace which contains all the
database related functions like public DataReader GetAllUsers() which
returns a datareader/dataset to the code-behind classes.
I use this methods in the DataAccess namespace from the codebehind
files to access data.
1) .aspx pages (presentation layer)
2) Codebehind and Base class files (logic)
3) DataAccess.cs (Data Access Layer)
(when I build the project all code compiled into a single .DLL file in
the /bin folder)
My doubt is, am I following the correct n-tier model?
Today I read an article in 4GuysFromRolla
http://aspnet.4guysfromrolla.com/articles/102302-1.aspx which
reccomends to use a separate business objects.
I'm really confused now
Can anybody advice me on this...... or please direct me to related article
Thanks and Regards,
Karthik Nataraaj
---------------------------------
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/
To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
