Enterprise Application Architecture with LINQ to SQL

using System;
using System.Linq;
using System.Data;
using System.Data.Linq;
using System.Collections.Generic;
using System.Text;
/*
 **************************************************************
 * Author: Rohit Gadagkar (rohit.gadagkar@gmail.com)
 * Copyright © 2007 Rohit Gadagkar
 * License:
 * Free without any restrictions whatsoever 
 *
 * Created: 9/1/2007
 * 
 * THIS CODE AND INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTY
 * OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
 * LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
 * FITNESS FOR A PARTICULAR PURPOSE.
 **************************************************************  
*/

namespace DLinqContext
{
    /// <summary>
    /// Impose the ICustomer contract for the Customer class that is autogenerated
    /// by the Orcas designer.
    /// </summary>
    /// <remarks>
    /// The Orcas designer generates a DBML file when database objects are dragged
    /// and dropped onto the design surface. Classes are generated behind the scenes
    /// to represent the ORM mapping defined in the designer. This involves attribute
    /// based mapping matadata, where a class and its properties are marked with
    /// attributes to associate with a database schema.
    /// 
    /// The ICustomer imposition is to make this class usable to the 
    /// CRUDGen<T> generic container class used for unit testing.
    /// </remarks>
    public partial class Customer : ICustomer { }




    /// <summary>
    /// Define a contructor override that takes both connection and mapping source
    /// </summary>
    public partial class northwindDataContext
    {
        public northwindDataContext(IDbConnection cn, MappingSource map)
            : base(cn, map)
        { }

    }
}