I previously blogged about the repository pattern and .NET implementations. Here are the links to those old posts: The Repository Pattern The Repository Pattern – Part 2 Since that time, I have zeroed in on a fairly
I often use a generic repository pattern as a wrapper around my data access logic. This wrapper generally serves the purpose of encapsulating specific implementation details. Here are the repository interfaces that I current use: public interface
I previously wrote about using the Repository Pattern with Linq to Fluent NHibernate and MySQL. Since that time, I have had the opportunity to refine and extend this approach. I have also noticed quite a few hits
I have deployed the Truck Tracker application to here for now: https://bobcravens.com/trucktracker/ The application is built using the following technologies: ASP.NET MVC Google Maps API v.3 jQuery DotNetOpenAuth MySQL NHibernate Ninject The intent of the application is
In a previous post we built a MySQL database and a data access layer via a repository pattern implemented using Fluent LINQT to NHibernate. We also wired up this repository in our ASP.NET MVC application using Ninject.
This is a continuation of a “truck tracker” sample application that leverages NHibernate as an object relational mapper (ORM). I previously created the entities, defined a repository interface, and implemented the repository using NHibernate. During this blog