3 tier architecture in ASP.NET
Hi..All..I want to design a 3 tire architecture in ASP.NET.I've gone through many sites and have understood the concept but I don't how to start it.
I've very basic questions like..how do I create the layer and How do I connect between the layers..
Would you please help and if you have any sample coding pls send it to me..
Thanxs
Tany
Re: 3 tier architecture in ASP.NET
I just happen to come cross this link which may not be what you are looking for but may still be helpful.
http://msdn.microsoft.com/data/dataa...tml/BOAGag.asp
Re: 3 tier architecture in ASP.NET
A simple way to start would be to sit down and think about the functionality of your application. Data Access logic should go in one layer, which could be a set of code files in a folder, or a Visual Studio Project that creates an assembly. This layer is used in all possible cases for marshalling data to and from the database. It doesn't know how to do anything else. Then you create another layer for business rules. I have a feeling most people are lax about creating a rich domain model. For small or learning applications its usually just a set of objects that conform to the tables in a database and carry data around. When working with serious business objects, that's where data mapping layers come in...if you've come across those yet.
Anyways, back on track. In the simple case, the business objects use the data layer to save and retrieve the data they contain. This can simply mean that the business layer project has a reference to the data layer project and the business layer classes instantiate and use methods provided by the data layer classes.
Same goes for the UI layer - it includes a reference to the business objects project. The UI project contains the webpages and code to perform actions requested by the user and to format the data. Except that the UI usually just forwards user requests to methods provided by the business objects. This way the UI is dependent upon the business objects, but the business objects don't know anything about the UI. Same thing with the business objects and data layer.
Re: 3 tier architecture in ASP.NET
I have a sample in my sig of a 3-tier thingy... :)
Re: 3 tier architecture in ASP.NET
Hi There,
Well, I think this might be an interesting article. it's in C#, but I believe it's helpful.
http://www.codeproject.com/aspnet/datier.asp
Re: 3 tier architecture in ASP.NET
Quote:
Originally Posted by MrMM
Hi there, you look familiar to me, welcome to the forums! :wave:
Re: 3 tier architecture in ASP.NET
Dee-u, have you updated your code already ??
Looking forward to see the updates you have done. My experience with MySQL is pretty good, and of course, its free !! :).
Greetings
Re: 3 tier architecture in ASP.NET
Hey..Thanxs,
I have complted my work in the 3 tier architecture..it's working fine..
If anybody wants the code,let me know.
RE: Add/Delete/Modify record in XML document in VB 6.0
Hi all..
I am doing application regarding XML and VB 6.0. I can able retrieve the data from XML document.
But how to add/delete/modify the records.
XML document format is :
- <Database>
- <emp>
- <Record>
<ename>Srikanth</ename>
<Eno>15</Eno>
<salary>85678678</salary>
</Record>
- <Record>
<ename>Madhuri</ename>
<Eno>16</Eno>
<salary>687678</salary>
</Record>
- <Record>
<ename>kalyan</ename>
<Eno>17</Eno>
<salary>567868</salary>
</Record>
- <Record>
<ename>Sree</ename>
<Eno>1</Eno>
<salary>111</salary>
</Record>
- <Record>
<ename>Anil</ename>
<Eno>2</Eno>
<salary>235345</salary>
</Record>
- <Record>
<ename>Madhu</ename>
<Eno>3</Eno>
<salary>43534</salary>
</Record>
- <Record>
<ename>aaa</ename>
<Eno>4</Eno>
<salary>234</salary>
</Record>
- <Record>
<ename>Kumar</ename>
<Eno>5</Eno>
<salary>2314123</salary>
</Record>
- <Record>
<ename>asdas</ename>
<Eno>6</Eno>
<salary>24312</salary>
</Record>
- <Record>
<ename>Madhuri</ename>
<Eno>7</Eno>
<salary>5675</salary>
</Record>
- <Record>
<ename>df sdfgdh</ename>
<Eno>8</Eno>
<salary>56456</salary>
</Record>
- <Record>
<ename>sdgfsd</ename>
<Eno>9</Eno>
<salary>45636</salary>
</Record>
- <Record>
<ename>asdfadf</ename>
<Eno>11</Eno>
<salary>34423</salary>
</Record>
- <Record>
<ename>sdfasg</ename>
<Eno>10</Eno>
<salary>4534</salary>
</Record>
- <Record>
<ename>cvbcvb</ename>
<Eno>12</Eno>
<salary>1423</salary>
</Record>
- <Record>
<ename>Srikanth</ename>
<Eno>13</Eno>
<salary>724958</salary>
</Record>
- <Record>
<ename>Olive</ename>
<Eno>14</Eno>
<salary>7897897</salary>
</Record>
</emp>
</Database>
In the VB 6.0 form i kept three textbox controls and three buttons like(Add, Delete,Modify).How to do operations plaese let me soon.
Re: 3 tier architecture in ASP.NET
Use the MSXML2 class library's DOMDocument object to work with XML files.
Re: 3 tier architecture in ASP.NET
hi
which version of VS you have used.
since sln is not opening in 2003.
Re: 3 tier architecture in ASP.NET
Quote:
Originally Posted by tany
Hey..Thanxs,
I have complted my work in the 3 tier architecture..it's working fine..
If anybody wants the code,let me know.
Send me the code of 3 tier architecture at my email address:
[email protected]
Thanks
Imran Ahmad Mughal
Re: 3 tier architecture in ASP.NET
This is insane. You can't just copy any three tiered architecture and modify it for your needs. That's worst than structured code. You must design your application to suit your needs. Go for a tutorial to understand OOP concepts, then design it yourself. This is absolutely insane. :eek:
Re: 3 tier architecture in ASP.NET
Quote:
Originally Posted by tany
Hey..Thanxs,
I have complted my work in the 3 tier architecture..it's working fine..
If anybody wants the code,let me know.
Can I see them? I'd like to see the code since you did say that all I do is ask. :wave:
I'd like to see it. Thanks. :D
Re: 3 tier architecture in ASP.NET
Quote:
Originally Posted by mendhak
This is insane. You can't just copy any three tiered architecture and modify it for your needs. That's worst than structured code. You must design your application to suit your needs. Go for a tutorial to understand OOP concepts, then design it yourself. This is absolutely insane. :eek:
It would be nice to see working applications. That's usually how I learn to c0d, concepts will remain concepts unless you see real working samples all interwoven nicely... or not. but that depends. :thumb:
Re: 3 tier architecture in ASP.NET
Yes, I did misunderstand.
Re: 3 tier architecture in ASP.NET
Quote:
Originally Posted by mendhak
Yes, I did misunderstand.
Good you correct your own misinterpretations. :thumb:
Re: 3 tier architecture in ASP.NET
Quote:
Originally Posted by dee-u
I have a sample in my sig of a 3-tier thingy... :)
hi i am deepak.
I need this sample. please let me know how can i get it..
Re: 3 tier architecture in ASP.NET
hi tany,
I was looking for 3-tier articles or base codes....Kindly send me the code.
my id is :[email protected]
Please do the needful.
Thank you
Quote:
Originally Posted by tany
Hey..Thanxs,
I have complted my work in the 3 tier architecture..it's working fine..
If anybody wants the code,let me know.
Re: 3 tier architecture in ASP.NET
This thread appears to be a case of the blind leading the blind (sorry if I have offended anyone who is actually blind).
There are two design aspects of any n-tier architecture: The logical design and the physical design. These address different issues or concerns. The logical design is done to attempt to make the code extensible and maintainable, and to get better reuse, easier coding, easier deployment, and so on. The physical design is to address scalability, fault tolerance, security, performance, and other similar concerns, most typically (but not always) in applications with a number of users.
It might be nice for a beginner to see some "3-tier" code example, but it won't be as productive as you might think - and could easily mislead you into thinking that the code is the important part of the model. The motivation and problems solved by the code is what is important.
Essentially, any simple code example of 3-tier or n-tier concepts might help you understand what is really mean by 3-tier, but I am doubtful that this will be any more helpful to you than reading a good book on the subject, and following through by writing a simple application of your own.
There are numerous books on the subject. One I will recommend that is very practical and nicely covers a number of the concerns while at the same time showing exactly how to do this in .NET (C# or VB.NET) is Rocky Lhotkas Expert Business Object books. He as VB6, VB.NET, and C# versions of the book (although the VB6 ones are long out of print). THESE ARE NOT BEGINNERS BOOKS. There is a lot covered that will only make sense to someone who has some experience and has either previously tried to solve the typical n-tier issues or has worked on a project where these issues were dealt with and solved by the architects/leads or whatever.