Finishing The Sample Project Using 3 Tier Architecture?
Oct 9, 2010
i ma new to asp.net, i am just learning asp.net using this site and some resources from internet , internet is the only source for me. and here i have a project that should be designed by the patter of 3 tier architecture. i have an idea, but i couldn't start it, need your guidance, if i did this , it will very useful for me to get a job.these are the requirements and steps.
When i create a new class on data layer,i can access that on business layer by creating object of that class.
but when i create a new "public class" on business layer i cant access that on presentation layer.
another thing is, after building business layer if copy Business.dll,Business.pdb,Data.dll and Data.pdb from business layer to presentation layer "BIN" i can access that class
recently i've studied on ADO.NET's Entity Model Framework and say 'wow' as ORM is one of the fevourite pattern i practice..but suddenly i've come to an ambiguous situation when i'm going to start. i usually follow the following 3-tier architecture..
1. UI Layer 2. BLL - business logic layer 3. DAL - Data Access Layer a. DTO / DAO b. Gateway (contains the sql query/stored procedure and connection with DB)
now when i'm going to use the Entity Model Design,where the DBML/ .edmx File should be placed? Because many a times i'm using the DBML file as DTO because of the mapped objects.. in the same time, sometimes DBML ( .edmx file in .NET 4.0) contains CRUD methods and stored procedured method as well as methods with different selection operations,- which should be in Gateway. so where the .edmx file should be placed !?!! IN DTO namespace !? or in Gateway namespace!
moreover sometimes there is no need for the BLL which breaks the rules of inter-layer-communication (UI > BLL > DAL.Gateway)! what makes me confuse is, what should be the ideal n-tier architecture when i'll use the ADO.NET Entity Model Design Framework
I am working on 3 tier architecture: UI, BL, DAL. In my UI i have following code for Asynchronous page processing:
[Code]....
But I want a database fetch operation to be performed in this asyncronous method. And due to 3 tier arch. i am unable to do this in UI Layer. Can anyone guide me that how can I implement Asynchronous processing in 3 tier architecture? Note: If you are going to place EndAsyncWork1 in DAL then show that how can I return a value back to UI layer from this function.
I want to know that What are the factors if we use methods on each .cs page for connection and executing query on each aspx code behind page rather then using BAL .
How our application get affected in terms of performance and speed or other way?
when we put our website on server after publish/compile in general approach (using query in C# code behind) rathor than using stored procedures?
I have implemented the 3-tier architecture project; DAL, BAL, and presentation layer are three layers in it. I am going to implement the following scenario:
Presentation layer calls to a function in the BAL layer which returns 2 string variable, and in turn this function from BAL layer calls to a DAL layer function which also returns 2 string variable. How can I implement the above scenario?
I'm developing a n-tier architecture... I'm confused with handling exception in the layers... Is it a good practise to add a Exception Layer to the architecture.
I am a newbie to asp.net and work in a firm where the projects are quite small.
I was told by my manager that in a few weeks or so we would be getting a bigger project and I need to be well versed with Design Patterns and N tier arcihtecture.
I would really appreciate if someone could provide me some links and also drop me a few sentences on how this things are useful?
I was tasked to create 3 tier web application. However, i browsed through many books & tutorials. The examples are doing it using Object data source which my lecturers claimed that it is not 3 tier at all. Shouldn't be dragging any data source into deisgn view. Any comprehensive examples for me to take reference from?
i want to develop an application in asp.net using 3 tier architecture .
i know that there are three layers
Data layerBusiness Layer
Data Access LayerBusiness Logic Layer Presentation Layer. I am confused between Data Access Layer and Business Logic Layer.
In data access layer we develop the property classes and main class function which returns datasets, datatables and data reader to Presentation layer.
what is the use of Business Logic Layer ? what actually we do in Business logic Layer ?? we can pass data directly from data access layer to presentation layer ?
(1).MSDN say that we should not have the namespace where its name is same with class name but it does not exlpain why.Does anyone know why? The msdn page is http://msdn.microsoft.com/en-us/library/893ke618%28VS.71%29.aspx
(2). Business Logic Layer BLTable1 need to interact with Data Access Layer DaTable1 , so i put the code: imports MyCompany.MyProject.DA. DaTable1 inside BLTable1, so that i can have access to all the public shared method inside DaTable1 in BLTable1 for example : DaTable1.Save()
But problem arise when BLTable1 want to use the public shared method in BLTable2 .
I have put the code imports MyCompany.MyProject.BL. BLTable2 inside BLTable1,but i need to key in the class name twice only can access to the public shared method inside BLTable2 for example :BLTable2.BLTable2.Save.
As per my understanding regarding N-Tier and SOA architecture.
N-Tier
N-Tier means dividing application into layers, Example I am developing application in asp.net and I pushed total DB Layer to WCF then it is called N-tier.[Tightly coupled]
SOA[Loosely coupled]
As per my understanding regarding SOA its very generic term and how well we going to loosely couple our architecture then its called SOA. Best example for SOA services - Stock feeds/ weather feeds.
My conclusion:
Even though if we develop application using WCF it does not mean its SOA if it is tightly couple with single client/ or .net applications only can understand about services.
Can you help me in understanding of SOA VS N-Tier.
In 3 tier architecture where to keep connection string? I have presentation layer ( webapplication) and BAL Layer ( class lib) and DAL (class lib).intially i kept in web.config which is in presentation layer....is it correct?should i keep a app.config file in DAL layer and keep my connection string in that?Where to keep connection string ?
My application was designed using following n-architecture : Presentation layer...wcf service layer...business logic layer..data access layer Presentation layer is in one server,wcf service,bll,dal are in another server. I knew something about wcf but how to implement this architecture.
I am looking for code sample for the above type of architecture.
How many tier architecture are there for ASP.NET?I know only one that is three tier architecture.Can anyone tell briefly about 4 tier architecture and other tier architecture?
I am implementing 3-tier architecture. I just wanted to know the role of business layer in 3-tier architecture.
I am developing application in using entity framework. So I have entity object which is accessiable in PL,BL & DL. My question is whether input assignment to entity object should be in PL OR BL.(Consider there is save method)
I'm developing one of my personal projects and I found some problem.
It's an n-tier architecture:
Framework. WCF Framework service. ASP.NET control that connects to the WCF Framework services in the server-side. ASP.NET client hosting that control.
WCF service is in ASP.NET compatibility mode.
What's the problem? Each request is in a different session. I found that because stored values for sessions are reseted in each request, as I stated before.
I've two questions then:
1) - Someway obvious but I want a confirmation - Does the fact of calling WCF Framework services in server-side mean that the session is for the server and not per client?
2) Is first question fact the reason of getting a new session after each request?
In the end, I'm about of disabling ASP.NET compatibility mode for that WCF Framework service and develop my own session state management, which isn't a hard task, but I'm not a friend of reinventing wheels.