3 Tier Architecture in ASP.net 2.0
Hi,
i am in the process to come out a 3 tier architecture for ASP.net 2.0
The Architecture that i want is
(1).DAL(Data Acess Layer) in App_Code folder
(2).BLL(Business Logic Layer) in App_Code folder
(3).Connection to Database in DAL is done through ObjectDataSource instead of TableAdapter, and SqlDataSource.
I have search in google for few days but still not able to get the sample architecture i want.
I understand the logic for the three 3tier, but how to do it programmatically is different .Does anyone has any idea on this?
Re: 3 Tier Architecture in ASP.net 2.0
Hi, i have come out the solution by using namespace.
Re: 3 Tier Architecture in ASP.net 2.0
Hi, i have come out a 3 tier architecture for Microsoft VB2005 for ASP.net Framework 2.0.
I have few question to ask on the 3 tier architecture that i have come out.
Below is my structure:
(1). Business Control Layer,Business Logic Layer, Data Access are all in App_Folder
where Business Control layer is to control user input error, Business Logic layer is to control logic error and Data Access Layer is to interact with SQL Server. This 3 layer communicate to each other using namespace.
For Example the flow for update, insert delete action to database is:
Presentation Layer-> BC layer (checking user input error) ->BL Layer (checking business logic error,open connection) ->DA Layer(Perform SQL action).
The Flow for read is Presentation Layer->BL Layer ->DA Layer.
My problem is how to control connection for every read that acess more than 1 table and resulted in more than 1 dataset in order to provide data to the presentation layer. The scenario is as below
Presentation Layer ->BL Layer ->DA Layer.
function getGUIDisplayData open connection function getGUIDisplayData
function getGUIDisplayData
For every function there is only 1 dataset return, if i open connection in BL Layer which mean that function getGUIDisplayData is only able to return 1 dataset for every read.If the presentation layer need more data than 1 data it seem that it is unlogic for keep on open and close connection which actually the connection should be open only once.
Does anyone has idea on how to control connection in read phase?
Thanks.
Re: 3 Tier Architecture in ASP.net 2.0
First of all, I'd close the connection to the database after every method. What if your program crahsed? Then you'll have an open connection.
Second, I recommend to study ADO.NET. You have way more options that just return 1 dataset per method.
Re: 3 Tier Architecture in ASP.net 2.0
I suggest you follow dannystommen's recommendations.
In C# you can use the 'using' construct when initialising your connection. This will ensure that the connection is closed automatically when it goes out of scope (even if an exception occurs).
I don't see why you would need more than one data set returned in each request. In a dataset you can have data from different tables. The dataset can be like an in memory representation of a sub-set of the data in the database. You can execute a query that will return data from different tables and fill a dataset with the data.
I suggest you go to MSDN or Google to find out more about ADO.NET. There are many examples...There is even an ADO.NET forum on this site when you find any problems in your implementation... :)
Re: 3 Tier Architecture in ASP.net 2.0
Hi dannystommen, nelo,
I have come out the solution for connection control in reading data from multiple table in database.
The solution is the DataAdapter will open/close the connection automatically for every read from tables in database. There is no need to code the open /close connection manually in the coding
Re: 3 Tier Architecture in ASP.net 2.0
