Data Access Layer
Data Access Layer in C# using Repository and Data Mapper – Part 4 The customer repository inherits the base repository and uses the data mapper instance for object creation. All the CRUD procedures defined in the first post of this series are called in this class. The query for accessing and persisting data in the relational model is formed in the Customer repository. protected override BaseMapper<Customer, long> Mapper get if (___Mapper == default(CustomerMapper)) ___Mapper = new CustomerMapper("CustomerIntId");
The GOF Template pattern coupled with .NET 2.0 Framework generics provides an awesome synergistic alliance. This article demonstrates how to drastically reduce the amount of code required in building a data access layer. Less code to debug... less code to break... less code to maintain... what could be better? An Elegant C# Data Access Layer using the Template Pattern and Generics
A Data Access Layer is an important layer in the architecture of any software. This layer is responsible for communicating with the underlying database. Making this layer provider independent can ensure multi database support with ease. This article discusses implementation of a provider independent Data Access Layer in C#. Implementing a Data Access Layer in C#
Interfaces + Factory pattern = Decoupled architecture - C#, ASP.Net, VB.Net Interfaces + Factory pattern = Decoupled architecture Introduction In this tutorial we will try to understand how we can use interfaces and factory pattern to create a truly decoupled architecture framework. In this sample we will take up a simple three tier architecture and apply interfaces and factory pattern to see how we can transform the three tier in to a truly decoupled architecture. For past some days I have been writing and recording videos in design patterns, UML, FPA, Enterprise blocks and lot you can watch the videos at http://www.questpond.com/
Practical Entity Framework for C#: Explore Entity Framework
The latest ADO.NET evolution focuses on raising the level of abstraction from the logical (relational) level to the conceptual (entity) level. For this purpose Microsoft introduces the Entity Framework, designed to simplify data - object conversion and embed data access queries into program code. The Devart dotConnect product line supports the ADO.NET Entity Framework for Oracle, MySQL, PostgreSQL, SQLite, DB2, and Salesforce. dotConnect data providers support all the Entity Framework versions - Entity Framework v1, v4, v5, and v6. Entity Framework Support
Devart Product Click on a price to enter the secure purchasing site and begin your order. As soon as we have been notified that your order has been processed, we will send you an email with your license number and further download information. dotConnect for Oracle can be registered under three types of licenses. You can get Single License for one developer, Team License for up to four developers, and Site License for an unlimited number of developers within a single company at one physical address. If you have other questions, please read our FAQ on License Agreement.
Feature summary NHibernate's primary feature is mapping from .NET classes to database tables (and from CLR data types to SQL data types). NHibernate also provides data query and retrieval facilities. NHibernate generates the SQL commands and relieves the developer from manual data set handling and object conversion, keeping the application portable to most SQL databases, with database portability delivered at very little performance overhead. NHibernate provides transparent persistence for Plain Old CLR Objects (POCOs). The only strict requirement for a persistent class is a no-argument constructor, which does not have to be public. NHibernate
The first and most dramatic performance problem that you can run into with NHibernate is if you are creating a new session factory for every session you create. Only one session factory instance should be created for each application execution and all sessions should be created by that factory. Along those lines, you should continue using the same session as long as it makes sense. best way to improve performance of NHibernate?