I would say, "No". The HTML page actually inherits from the CodeBehind document, so technically, these represent one object of the presentation layer. This rules out the CodeBehind as a separate BusinessLogic layer.
The DataSet is basically a disconnected view of the database. It cannot extract data from the database without a DataAdapter, nor can it commit data back. Therefore, it cannot really "access" data. Since it cannot fulfill the definition of a DataAccess layer without the assistance of other objects, I don't think it could be considered a DataAccess layer. William Alexander Software Developer ----------------------------------------------- DATATRAK International, Inc. 6150 Parkland Blvd. Suite 100 Mayfield Heights, OH 44124 P - (440) 443-0082 F - (440) 442-3482 -----Original Message----- From: Thomas [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 22, 2002 7:12 PM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Code behind as business object layer I am curious about something. This is a bit odd. In a typical layered application scenario, especially web app, there are presentation, business and data access layers, as well as a data storage layer. Could one make the argument that in an asp.net app these layers are embodied in a aspx page with a code behind file that uses a dataset or extended dataset? The html portion (or design surface) of the aspx page being the presentation, the code behind being a business object layer and the dataset(s) being the data access layer. And if some additional level of abstraction is needed an extended DS can be put between the data access DS and the page itself. Thanks, Thomas You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
