.NET (Core and Framework)

Pete O'Hanlon6-Oct-10 1:14

6-Oct-10 1:14

Strictly speaking, you want to be looking at n-tier architecture because you may not end up limiting yourself to 3 physical tiers. If you want to implement a multi-tier system, then I would recommend reading up on the subject first - possibly starting with Rocky Lhotka's excellent work on CSLA.

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

ely_bob7-Oct-10 4:06

ely_bob

7-Oct-10 4:06

Rocky's Website[^].

I'd blame it on the Brain farts.. But let's be honest, it really is more like a Methane factory between my ears some days then it is anything else...

-"The conversations he was having with himself were becoming ominous."-.. On the radio...

Pete O'Hanlon7-Oct-10 4:42

7-Oct-10 4:42

Shouldn't you post this where the OP gets notified of it?

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

Re: three tire architecture [modified]

ely_bob7-Oct-10 5:46

ely_bob

7-Oct-10 5:46

I'm a big fan of structured data... Poke tongue | ;-P

ohh and Rocky is in the office today... Big Grin | :-D

modified on Thursday, October 7, 2010 12:10 PM

Pete O'Hanlon7-Oct-10 6:17

7-Oct-10 6:17

Well, that's good. I'm still not the OP.

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

Luc Pattyn6-Oct-10 2:06

Luc Pattyn

6-Oct-10 2:06

Maybe these will help:
Building an N-Tier Application in VB.NET, in 8 Steps[^]
http://msdn.microsoft.com/en-us/library/bb384570.aspx[^]

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Abhinav S6-Oct-10 5:38

Abhinav S

6-Oct-10 5:38

See here[^].

The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.

My latest tip/trick

Visit the Hindi forum here.

Pavel Yermalovich6-Oct-10 10:26

Pavel Yermalovich

6-Oct-10 10:26

So, first you create an empty solution. Then you add three projects into it. The first one is ASP.NET applcation which will be your PL (Presentation Level) and two class library for DAL and BLL. In DAL you will add LINQ to SQL class as one of possible way to map your database. Will create for every entity the class with the name YourEntityData to implement CRUD methods. Also you can add CustomizedEntites.cs file to extend your LINQ entities. In BLL you'll develop your business objects. As a rule every class includes MapToCustomProperties(Entity entity) for DAL->BLL mapping, MapToEntity() for BLL->DAL mapping and Load() to load information for object from DB. Often in the same file i create and write collection class for this object. F.e. ProductBLL and ProductBLLList:List<productbll>. In your PL tier you are working just with BLL tier and so on...

AspDotNetDev6-Oct-10 21:03

AspDotNetDev

6-Oct-10 21:03

That's a popular subject right now; you've picked a good year to ask this question. Take each reply with a grain of salt, and remember that a good design should not affect the Big O performance of your application.

[Forum Guidelines]

Alexander DiMauro7-Oct-10 2:09

Alexander DiMauro

7-Oct-10 2:09

There is a new book from Wrox called ASP.NET Design Patterns[^] that covers this pretty well. Here is an excerpt from the TOC:

Part 2: The Anatomy of an ASP.NET Application: Learning and Applying Patterns

3. Layering Your Application
4. Business Logic Layer: Organisation
5. Business Logic Layer: Patterns
6. Service Layer
7. Data Access Layer
8. Presentation Layer
9. User Experience Layer

Part 3 even includes a case study.

We live in a world operated by science and technology. We have also arranged things so that almost no one understands science and technology. This is a prescription for disaster. We might get away with it for a while, but sooner or later this combustible mixture of ignorance and power is going to blow up in our faces.
--Carl Sagan

ely_bob7-Oct-10 8:24

ely_bob

7-Oct-10 8:24

Rock'y approach has been received very well in the community.

He has a number of books, and video's available on http://www.lhotka.net/[^].

-- for Pete $Shucks | :-\$

Pete O'Hanlon7-Oct-10 11:50

7-Oct-10 11:50

And Pete says "sorted". Thumbs Up | :thumbsup:

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

urgent plz

mmaryum4-Oct-10 22:29

mmaryum

4-Oct-10 22:29

hi kindly tell me names of software system that are changed frequently(their new versions are updated frequently)and their documentation got old (documentation is not updated with the changings in software)

Rajesh Anuhya4-Oct-10 23:33

Rajesh Anuhya

4-Oct-10 23:33

Rajesh B --> A Poor Workman Blames His Tools <--

Dave Kreskowiak5-Oct-10 1:07

Dave Kreskowiak

5-Oct-10 1:07

Uhhh, no.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

Pete O'Hanlon5-Oct-10 1:22

5-Oct-10 1:22

Well, there were Fred, Ginger and Algy. We mustn't forget Bob or Rita either.

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

This is where a useful subject line should go

Luc Pattyn5-Oct-10 2:07

Luc Pattyn

5-Oct-10 2:07

Hi,

you're new to CodeProject, and apparently you forgot to read the "how to get an answer" message on top of this forum. I think you should do so now if you ever want to get any results on future enquiries.

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

JFDR_027-Oct-10 5:02

JFDR_02

7-Oct-10 5:02

So what you're looking for is a name that describes a piece of software that is changed often by the developer(s) but said developer(s) do(es)n't update the documentation to reflect those changes?

Hmm.... Agile Development perhaps? Or VB development?

I actually don't know. And I didn't know it had a name either. It pretty much describes process at the place where I work.