Skip to main content

Entity framework practices

People who are using entity framework for Dal single dbcontext is going to be a problem in BLL. I use the following structure

 

I used to get the single dbContext by:- Each single repo class should inherit from base repo class and in base repo class should initialise the dbcontext.

 

The BaseRepository

 

  public class BaseRepo

    {

       private readonly bool isNewInstance;

       protected OnlineProductLinkEntitiesdbContext;

 

 

       protected BaseRepository()

       {

           dbContext = newOnlineProductLinkEntities();

           isNewInstance = true;

       }

 

       protectedBaseRepository(OnlineProductLinkEntitiesdbContext)

       {

           isNewInstance = dbContext == null;

 

           if (isNewInstance)

               dbContext = newOnlineProductLinkEntities();

 

           this.dbContext = dbContext;

       }

 

       protected voidCheckAndTryToOpenConnection()

       {

           if (dbContext == null)

               dbContext = newOnlineProductLinkEntities();

           if (dbContext.Connection.State !=ConnectionState.Open)

               dbContext.Connection.Open();

       }

 

       public void Dispose()

       {

           if ((!isNewInstance) || (dbContext ==null))

               return;

 

           OnlineProductLinkEntities context = (OnlineProductLinkEntities)dbContext;

 

           if (context.Connection.State ==ConnectionState.Open)

           {

               context.Connection.Close();

           }

 

           context.Dispose();

           dbContext=null; 

       }

}

 

The single repo class constructor looks like

 

    public Cmo_SiteRepository(){}  

 

    public singleRepo (OnlineProductLinkEntitiesdbContext):base(dbContext), Irepository<model, entity>

       { }

 

 

A method inside the single repo class will look like this

 

    public int Create(SiteModel model)

       {

           try

           {

               CheckAndTryToOpenConnection();

               objectTable siteEntity = newobjectTable ();

           }

           catch (Exception ex)

           {

               throw new Exception("Exception", ex);

           }

       }

 

 

Comments

Post a Comment

Popular posts from this blog

Compiled Query- Improve the performance of Linq to Entity Query

Most of the small or medium IT firms are using the Entity framework for the Data Access layer (DAL). If we write a complex linq to Entity queries performance will always be an issue. But with the Compiled Query Performance can be improved. This below definitions are from MSDN and more details can be found on the MSDN Link that is at the end of this post           When you have an application that executes structurally similar queries many times in the Entity Framework, you can frequently increase performance by compiling the query one time and executing it several times with different parameters. For example, an application might have to retrieve all the QuoteRevision for a particular quotelineStatus, the quotelinestatus is specified at runtime. LINQ to Entities supports using compiled queries for this purpose.               The  compiled query class provides compilation and caching of queries for reuse . Co...
1 comment
Read more

Sql Server Internals - Named Pipes

Named pipes enables clients applications to request a reliable and two way connection between the client application and Sql Server, across a network. A named pipe has a name which follows the UNC naming convention : \\Server\pipe\name The default names pipe for SQL server is :                 \\Server\pipe\sql\query A named instance would have a named pipe of                \\server\pipe\MSSQL$instancename\sql\query Early versions of SQL Server only provided Named Pipes. Named Pipes also allows for impersonation of a clients credentials. The feature is used by SQL server when using Linked Servers. The clients logon credentials are passed across to the Linked Server for authentication. Named Pipes can operate over TCP/IP, NETBEUI or IPX as it indirectly relies on the Common Internet Files Sytems
Post a Comment
Read more

Bootstrap Server Side Pagination - alternative to data tables

Background Most of the Web developers are familiar with the Datatable.Net for pagination. DataTables can integrate seamlessly with  Bootstrap  using Bootstrap's  table styling options  to present a consistent interface with your Bootstrap driven site / app. The main disadvantage with Data table.net is it is applying the pagination at the client side and for the large data set it can take minutes to load the data. Like every other designer I also faced the problem with Data table.net. So what is the best option to replace the client side paging and searching. So I forced to create a custom module to do the pagination and searching. The below sample don’t support the sorting, but got an option to extend the functionality. Please check my Next Post for sorting functionality The technologies used include, MVC 4.0, HTML5, Bootstarp.css, Knockout. js, Ajax, Web Api 2.0, Linq to SQL and C#. Knockout.js Model’s Filter Model var filter = function (...
Post a Comment
Read more