Last post Oct 05, 2010 03:01 PM by atconway
Oct 05, 2010 02:32 AM|btechathi|LINK
Can any one explain me that what is standard bussiness login in asp.net..
Recently, I went to the asp.net interview and the interviewer asked me to develop a page with db connections..
and end of the time, The interviewer asked me to build business logic code in asp.net.. even i have created 2 classes for that interview and i have used only store procedures.. So I am really get confused about business logic.. Please explain me and give
me some web pages link which is having sample code for standard bussiness logic...
Thanks & Regards,
Oct 05, 2010 02:42 AM|dk_4_asp|LINK
try learning building application in 3-tier architecture...........just google about 3-tier architecture and you will get sufficient information.
Mark as answer if it helps you.
Oct 05, 2010 06:50 AM|Vikram_AspNet|LINK
You need to get knowledge of application layers like UI, Data access , Business layers.
Please go through the following links:
Oct 05, 2010 07:26 AM|riswadkarharshad|LINK
IMO, the business logic layer contains classes that maps to the db table. E.g. we may have a customer table in db and have Customer class in BLL that have properties matching with customer table.
As per the business requirement, we may also add any code to BLL that checks for certain validation like participant must be 18+ years to register with site.
Oct 05, 2010 07:38 AM|toas1|LINK
Can any one explain me that what is standard bussiness login in asp.net
I suppose you mean "...standard business logic..."? If thats what you ask about I would say there is no such thing as "standard business logic". or maybe I should say, I have never seen business logic that are the same for every domain...
For me, in a very simplified way, busniess logic is the set of rules that builds up the business domain. These rules might be extracted out from some kind of interaction with your application, maybe based on a use case or some other interaction (that could
be internal with in the application or between yours and other applications). A business rule might be as easy as assert that a value is in the correct format or a very complex chain of events. And just as you said they might very well be implemented in stored
procedures in a database (I only say they could, but thats not how I would do it).
A very good start is to read Eric Evans book,
domain driven design
Oct 05, 2010 03:01 PM|atconway|LINK
The interviewer asked me to build business logic code in asp.net..
It sounds like the interviewer was trying to touch on your understanding of building an ASP.NET application using a traditional 3-layer architecture which consists of a User Interface Layer (UI), Business Logic Layer (BLL), and Data Access Layer (DAL).
As you can see the Business Logic (layer) is the middle layer in this architecture. This layer is responsible for several operations including communication between the UI and the DAL and executing business rules against business objects and the data coming
in from either end.
Typically in a nutshell the DAL will extract the data and package it up, the BLL will manipulate the data based on business needs and potentially create business objects based on the logical model and not necessarily the one of the physical database structure,
and the UI will consume and bind the data. Of course there is a lot more going on than just these parts, but these are the high points. The BLL specifically isolates the logic of the application and should be independent of the UI and database technologies.
This will allow you to change the way the app communicates to the database or binds to the UI without effecting the primary logic of the application. The BLL acts as the intermediary for communication between the (2) layers.
Below are (2) decent tutorials written on creating a BLL and a DAL. Take a look at them, and after understanding the purpose better, then apply that to your individual application.
Creating a Business Logic Layer:
Here are some generic high level definitions that may help as well.
Business logic layer: