You searched for the word(s): userid:870220

More Search Options

RSS Available

• is it matter of taste only - typed datasets

  Considerng below all issues with strongly typed dataset why Scott Mitchell have prepared tutorial on DataAccess http://www.asp.net/learn/data-access/ , is it all matter of taste of or self preference or its just for getting started for novice developers? I want to know that is it no difference architecture point of view to chose between Strongly Typed Data Set DataSet Custom Entities Typed Datasets Issues 1. Consumes more memory as collection of data sets 2. It goes complex as database goes and costs

  Posted to Data Access and ObjectDataSource Control (Forum) by sarfraz_khari on 7/16/2009
  Filed under: typed data set

• Re: Exception Handling Model

  public void Application_Error(object s, EventArgs ev){ StringBuilder message = new StringBuilder(); if (Server != null) { Exception e; for (e = Server.GetLastError(); e != null; e = e.InnerException) { message.AppendFormat("{0}: {1}{2}", e.GetType().FullName, e.Message, e.StackTrace); } //Log the exception and inner exception information. }} Moreover ASP.NET provides several levels at which you can handle and respond to errors that may occur when you run an ASP.NET application. ASP.NET

  Posted to Architecture (Forum) by sarfraz_khari on 7/15/2009
  Filed under: Exception Handling asp.net

• Re: Business Entities and Business Logic Layer

  Yes defining Business Entities as spate project is more appropriate, Code reusability is possible this way. Business Entities can be referenced in both UI and BLL but refereeing and using in DAL is not recommended because DAL should only behave like data utility layer.

  Posted to Architecture (Forum) by sarfraz_khari on 7/9/2009

• Re: BLL -Dataset or class?

  Initially it seems that it’s overhead to replace Datasets with custom objects but actually its not, DataSet are in huge memory because they much other information with them which is normally not needed. Moreover as you are using BLL in your application, it is beneficial for you to use Custom Objects as in case if your data-source (SQL) changed to some other you merely only have to change your DAL and somewhat BLL; there will be no change in UI layer. There are also other benefits in using custom

  Posted to Architecture (Forum) by sarfraz_khari on 7/8/2009
  Filed under: business enitities, datasets vs Custom Objects

• LINQ or Enterprise Library or ADO.NET Entity Framework

  I am going to new desktop project; project specification is below: 1. Desktop application 2. Will be build on Relational Database 3. Database design is just plain and straightforword 4. Application will be deplyed as one package (Client + BLL + DLL) 5. No web services need in Business layer. So far now i am habitual of using Enterprize Library as Data Access. I found on different blogs that LINQ and Entity Framework are also getting utilized in no. of projects. Presently i have design so (UI Layer

  Posted to Architecture (Forum) by sarfraz_khari on 7/1/2009
  Filed under: ADO.NET, linq, Enterprise Library

• Exception Handling and Logging Best Way

  I am writing a desktop application that has three layers, where in each layer there is the possibility of Exceptions being occured. Where it is best way to handle an exception if it is raised in a lower layer, such as the data layer or Business Layer? For example, I have the following layers. Note: I am using Enterprise Library 4.1for exception and logging block, library practice allows me to handle it at any layer, Now question is that at which layer it should be handled. UI Layer (WinForm) ->

  Posted to Architecture (Forum) by sarfraz_khari on 6/30/2009
  Filed under: Exception Handling Application Block

• Re: best practice on loading data to UI

  Like in GridView in which we are loading "Location" as dropdown on RowDataBound event in that case for each "Domain" row a trip to DB is required for displaying relevent "Location" as well as other location items in "Location" dropdown, for binding 50 rows of domain some lazy code will definately have to trip 50 times to DB. I suggests presists or place "Location" recordset in some object on page using caching or other. Bring Location data on first

  Posted to Architecture (Forum) by sarfraz_khari on 6/30/2009