Getting Started

Re: need suggestions

mudassarkhan — Mon, 06 Jul 2009 05:32:50 GMT

You don't need to close or open everything is handled by that MS Lib you just need to call ur Stored proc or queries and get results

Refer these articles

http://forums.asp.net/122.aspx

http://www.4guysfromrolla.com/articles/070203-1.aspx

http://www.codeproject.com/KB/database/MS_Application_Blocks.aspx

http://www.aspfree.com/c/a/ASP.NET/Developing-ASPNET-20-Applications-with-the-Microsoft-Data-Access-Application-Block/

Re: need suggestions

safzal1212 — Mon, 06 Jul 2009 05:15:36 GMT

Can you please elaborate your question a bit. The only suggestion that I can give to you is use n-tier architecuture if you have a good size project. If the application you are writting is small then don't use n-tier. In case of small size project create folders for classes inside app_code folder and don't add multiple tiers. I would recommend stored procedures in any case.

Re: need suggestions

vikvish1 — Mon, 06 Jul 2009 04:59:05 GMT

thanks for reply...

but reply my following question if u know..

Where I can find software or website addess which tell me / or shows me what kind of the errors in my web site and which code I copied…? and also show me or tell me which scripts is open ot close....

i have downloaded and install the Data Access Application Block software.. but its not runnin properly

wel i m using asp.net 2.0 with sql server 2005.

will wait for your reply

with regards

vik

Re: need suggestions

mudassarkhan — Sun, 05 Jul 2009 08:03:41 GMT

1. Get or Create a Datahelper library. You can download MS Data Access Block which will take care of all connection related issues

http://www.microsoft.com/downloads/details.aspx?FamilyID=f63d1f0a-9877-4a7b-88ec-0426b48df275

2. Create a Data Access Layer to execute stored procs (Create a Class Library)

3. Create Business Layer to perform busniess logic, validations and call the Data Access Layer methods (Create a Class Library)

4. UI will call the Business layer methods

Thus this leads to 3 layer architecture

Re: need suggestions

srinivaskotra — Sun, 05 Jul 2009 07:25:28 GMT

Hi,

this link will brief you about three trir architecture and samples

http://www.beansoftware.com/ASP.NET-Tutorials/Three-Tier-Architecture.aspx

http://www.codeproject.com/KB/architecture/three_tier_architecture.aspx

Thanks :)

Re: need suggestions

hs_jha — Sun, 05 Jul 2009 05:27:30 GMT

vikvish1 ,

A sizable portion of software industry works on software maintenance.This needs you to work in team , have a planned arrchitecture.There are times when you need to understand and complete the leftovers of the programmer who worked previously. This needs a standard pattern which every one can understand.This is where you need an architecture.3 tier is the most popular one but there are couple more like MVC architecture as well.

There is no problem if you do not adopt these architecture and go on coding like what is called a bare-bone programming for your personal applications.But when you return back to your codes after 2-3 years to improve it you may not remember where you had written what.

So better go systematic than random to plan a system.

This forum has a very nice tutorial series by Scott Mitchell for 3 tier architecture at

http://www.asp.net/learn/data-access/?lang=cs

Re: need suggestions

abdelnaby — Sat, 04 Jul 2009 18:47:53 GMT

use linQ

Re: need suggestions

Segundo — Sat, 04 Jul 2009 16:14:55 GMT

Hi,

Here is a good serie of articles about layered applications:

http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=476

Any doubt, post your comment.

Re: need suggestions

ctheriault — Sat, 04 Jul 2009 15:09:20 GMT

The strategy of n-Tiers (3-tiers) architecture, is develop your application in layers which are communicating with each other using a simple (and well documented) interface. It purpose is to insulate the complexity and rules within each layer to avoid having side effect on other layers.

For example:

if your "data access" layer is over Oracle, and you decide to change it later for "Linq over SQL-Server", you would re-engineer only this layer, without any impact on the rest of the application (presentation layer + business rules layer)
if your presentation layer is Windows form and you want to change for ASP.NET, Silverlight, AJAX, ..., you should be able to reuse near 100% of the data access layer and business rules layer.
and so on

n-Tier architecture is also convenience to slip up the work between many software development teams, each layer is like a sub-product.

That you choose to use SQL (strored proc) or C# to implement business logic is a decision that should be made taking "maintenance" into consideration, and sometimes performance depending if you want to move load to your DB server or from your DB server. Chosing one way or the other should be a balanced decision. I personnaly often chose to perform the processing in C# because it is powerful to create dynamic query (espicially with LINQ), but I also have store procs to handle some critical parts in T-SQL to spare network communication overheat with DB server.

Re: need suggestions

nijhawan.saurabh — Sat, 04 Jul 2009 11:17:21 GMT

Three tier applications are basically for supporting development(making development of a project in a team simpler) and has nothing to do with performence.

More over 3 tier technique helps in code reuse and hence further helps you in a way!

need suggestions

vikvish1 — Sat, 04 Jul 2009 05:39:16 GMT

Hello there..

I have questions and hoping for reply

Well I am working asp.net 2.0 with ajaxtoolkit

What is the best approach to coding… like in three architecture…? Like class file

store procedure and coding…

if we not work like three architecture then is there any difference.. if we do jst coding and use aonly procedures with con.open and con.close..? any drawbacks?
Where I can find software or website addess which tell me / or shows me what kind of the errors in my web site and which code I copied…?

Hoping for reply

With Regards

vik