.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
Easy Web
Imran Ghani
Post New Web Links

Data Points: The Enterprise Library Data Access Application Block, Part 3

Posted By:      Posted Date: August 21, 2010    Points: 0   Category :ASP.Net
 

E nterprise applications can have a wide variety of data update requirements. Sometimes you need to save multiple rows of changes at once within a single transaction. Other times, the user must be allowed to enter multiple rows of data, send them to the database in a batch; and if a row or two fails, only the rows that succeeded should be committed and remain committed.

John Papa

MSDN Magazine October 2005




View Complete Post


More Related Resource Links

Data Points: The Enterprise Library Data Access Application Block, Part 2

  

Last month I explored the foundation of the Enterprise Library Data Access Application Block (DAAB) including how it all fits into an architecture (see Data Points: The Enterprise Library Data Access Application Block, Part 1).

John Papa

MSDN Magazine August 2005


Data Points: The Enterprise Library Data Access Application Block, Part 1

  

A solid data access later (DAL) can benefit an application by hiding redundant tasks, helping handle exceptions more gracefully, helping clean up resources more efficiently, and providing a layer of abstraction from the database.

John Papa

MSDN Magazine July 2005


MVC architecture in ASP.Net using C# and Microsoft Data Access Application block

  
The Model-View-Controller (MVC) pattern separates the modeling of the domain, the presentation, and the actions based on user input into three separate classes [Burbeck92]:

Model. The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller).

View. The view manages the display of information.

Controller. The controller interprets the mouse and keyboard inputs from the user, informing the model and/or the view to change as appropriate.

Microsoft Application Block for Data Access in .NET

  

Hi all,

I was rummaging the internet learning aspx and came across the concept of: Microsoft Application Block for Data Access in .NET

It seems great of course. The articles are all early 2003-5 such as

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

So the question is - is this tech still relevant and should I be using it?

Thanks,

Mat



Using Data View Web Part to access Documents in Separate Web Application

  

MOSS 2007 SP2
SharePoint Designer 2007

I am currently trying to display the contents of a document library within a separate site collection (different Web Application). The source document library is hosted on a Records Center on a Web Application with a name of records.example.com. The destination site (where the documents need to be displayed) is on a Web Application named teamsite.example.com

I am thinking web services is the way to go, but when I setup a connection to records.example.com/_vti_bin/Lists.asmx, I receive an error when trying to get the data:

The server returned a non-specific error when trying to get data from the data source. Check the format and content of your query and try again.

Any help will be greatly appreciated!


how to write wrapper for Data block of Enterprise library

  

Hi,

 

I have the following scenario.

The project has 4 layers

1) Business Entities

2)Business Layer

3)DataLayer

all are separate projects
so lets say

1 )Business Entities has
 

public class Employee
{
public int EmpId{get;set;}
public string EmpName{get;set}
pullic int Age{get;set;}
}

2)Business layer will call dataacess layer

public class BusinessLayer
{

public int RegisterEmployee(Employee objEmp)
{
 Datalayer objDal =new Datalayer();
 objDal.AddEmployee(objEmp)

}
}


3)From the datalayer i need to call Wrapper for enterprise library and the requirement is
datalayer should not have any reference of Enterprise library data block(that i dont know how to do that)
Only the wrapper class should have reference for Enterprise library data block

so

public class Datalayer
{
 public int AddEmployee(Employee objEmp)
{
///Database db=DatabaseFactor.Createdatabase()
//the above line should not be in datalayer it should in some other componenent
//lets say component is wrapper
//i want to how to write wrapper for that.
//As well as how to build command and parameter
}
}


 

 


Data Truncation issue with Enterprise Library Logging WriteLog stored Proc

  

Hi ,

I'm using Enterprise Library Logging  feature for logging. The issue i am facing is when the Logging message is too large(more than 65534 chars) ,complete data  is not logged in the Formatted Mesage column which is  of data Type nText .

I am able insert complete data if i try inserting from Sql insert Query from sql management studio. Do i need to add any attributes to data base listener or do i need to change the sp.

 Is there any way to increase the WriteLog stored proc param size in EnterpriseLibrary.Logging config file ? . Please let me know.

 

Thanks In Advance.


data access library v4.1

  

Ive just started a project that will use the enterprise library 4.1 data access code blocks.  Its been years since ive used them, can anyone tell me what assemblies I need to reference in my project in order to use them ?  Ive referenced 


Microsoft.Practices.EnterpriseLibrary.Data


are there any others I need ?


Data Points: Deny Table Access to the Entity Framework Without Causing a Mutiny

  

Julie Lerman shows database administrators how to limit access to databases from the Entity Framework by allowing it to work only with views and stored procedures instead of tables-without impacting application code or alienating developers.

Julie Lerman

MSDN Magazine August 2010


Data Access: Building a Desktop To-Do Application with NHibernate

  

Building an NHibernate-based desktop application isn't any harder than building a web application, and in many cases NHibernate simplifies elements of session handling and concurrency.

Oren Eini

MSDN Magazine December 2009


Data Points: Accessing Data from a Mobile Application

  

This month John Papa takes a look at developing a mobile application that can access data on your application server.

John Papa

MSDN Magazine January 2008


Data Points: Data Access Strategies Using ADO.NET and SQL

  

When your goal is a scalable and efficient enterprise solution, you need to develop an efficient data-access strategy. You can't just do some testing on your production machines and rely on the results.

John Papa

MSDN Magazine May 2005


Data Points: Handling Data Concurrency Using ADO.NET, Part 2

  

Enterprise development has been moving towards a discon-nected model in recent years and ADO. NET development is no exception. While the disconnected model of the ADO. NET DataSet offers great flexibility, that adaptability also means looser control over data updates than you get with a connected data access model.

John Papa

MSDN Magazine October 2004


Data Points: Migrating from ADO to ADO.NET, Part 2

  

As you move forward with your use of ADO. NET, you'll need to know how to approach situations that you previously learned to handle in ADO and now have to tackle with ADO. NET. Just as n-tiered solutions developed using Visual Basic®, C++, and ASP often rely on ADO for their data access needs, Windows® Forms, Web Forms, and Web services rely on ADO.

John Papa

MSDN Magazine August 2004


SharePoint Portal Server 2001: Search and Access Disparate Data Repositories in Your Enterprise

  

The knowledge worker is greatly empowered if she is able to access information across the enterprise from a central access point. With the SharePoint Portal Server 2001 Search Service you can catalogue information stored in Exchange public folders, on the Web, in the file system, and even in Lotus Notes databases. This article discusses the use of ActiveX Data Objects and the Web-based Distributed Authoring and Versioning protocol for creating search solutions based on SharePoint Portal Server 2001.

Kayode Dada

MSDN Magazine April 2002


Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend