Types of Design Patterns:
I. Creational
II. Structural
III. Behavioral

I. Creational Patterns:
1. Abstract Factory - Provide an interface for creating families of related or dependent objects without specifying their concrete classes.

2. Builder - Separate the construction of a complex object from its representation so that the same construction process can create different representations.

3. Factory Method - Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.

4. Prototype - Specify the kind of objects to create using a prototypical instance, and create new objects by copying this prototype.

5. Singleton - Ensure a class has only one instance and provide a global point of access to it.

II. Structural Patterns:
1. Adapter - Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn’t otherwise because of incompatible interfaces.

Members and Methods:
Equals
Finalize
GetHashCode
GetType
ReferenceEquals
ToString

What is enum: enumuration is comprised of a number of named constants.

Creating Enumuration :
public enum UIType
{
None,
Label,
DropDown,
TextBox,
CheckBox,
ListBox,
DateTimePicker
}

Convert Enumuration Item to string :
string itemValue = UIType.CheckBox.ToString();

Convert string to Enumuration instance:
returnValue = (UIType)Enum.Parse(typeof(UIType), str, true);

Note:
// While parsing enum it throws an ArgumentException if the string is found not to be one of the members of the enum. you must handle it.

Iterating Enum and reading data from Enum:
foreach (string s in Enum.GetNames( typeof(UIType)))
dropdownlist1.Items.Add(s);

Convert integer to Enum instance:
UIType chkbox=(UIType)Enum.ToObject(typeof(UIType), (int)UIType.CheckBox);

A schema is nothing more than a named, logical container in which you can create database objects. A new schema is created using the CREATE SCHEMA DDL statement. Beginning in SQL Server 2005, each object belongs to a database schema. A database schema is a distinct namespace that is separate from a database user. Schemas can be created and altered in a database, and users can be granted access to a schema. A schema can be owned by any user, and schema ownership is transferable.

SQL Server 2005 has given us the ability to create schemas independent of the user, and by this we achieve separation of schemas and users. This gives us some considerable advantages:

1. The first benefit is the ability to subdivide your database into logic of interest, rather as the Erwin modeling tool lets you create subject areas.
2. You can provide better security at Schema level.
3. Dropping database users is greatly simplified; dropping a database user does not require the renaming of objects contained by that user’s schema. Thus it is no longer necessary to revise and test applications that refer explicitly to schema-contained objects after dropping the user that created them
4. Multiple users can share a single default schema for uniform name resolution.
5. Shared default schemas allow developers to store shared objects in a schema created specifically for a specific application, rather than in the DBO schema
6. Permissions on schemas and schema-contained objects can be managed with a higher degree of granularity than in earlier releases.
7. Fully qualified name of object in SQL Server 2000 and earlier looks like
   [Server].[DatabaseName].[OwnerName].[ObjectName]
8. SQL Server 2005’s fully qualified name for object looks like below
   [Server].[DatabaseName].[Schema].[ObjectName]
9. You can able to transfer Schema ownership

Creating schema
CREATE SCHEMA Marketing
GO

Adding table object

CREATE TABLE Marketing.Leads

(
    LeadId INT,
    LeadDescription NVARCHAR(50)
)
GO

Accessing table object

SELECT * FROM Marketing.Leads
GO

After you have created schemas, your database looks like below

Simple steps to generate help files for your assemblies 
=====================================
I. Softwares to be installed:
SandCastle - http://www.codeplex.com/Sandcastle
SandCstle help file builder - http://www.codeplex.com/SHFB

II. Configuration in Visual studio
Configure Visual studio to generate XML comment file along with assemblies

Project properties -> Build tab -> check “XML documentation file”

III. Configure SandCastle Help Builder
Create a new project and add your assembly to the project. Once you added assemblyname it appears with xml comment file. It looks like ”MyAssembly.dll, MyAssembly.xml”.

IV. Finally build help file
In SandCastle Help Builder -> Goto “Documentation” menu -> Build Project

Once you build project, It saves help project file as well once it gets build you will have your html help file.

SubSonic step by step

I. SubSonic is a toolset that helps to

1. Generate DAL layer
2. Maintains and Generates SQL Script for DB Versioning
3. Dynamic Query tool helps to use SQL Server etc without knowing SQL
4. OR Mapper that extends to views and stored procedures

II. Installation

1. Download SubSonic @ http://www.codeplex.com/subsonic/Release/ProjectReleases.aspx?ReleaseId=5636
2. Install SubSonic by walking through steps, by default it stores at “Program Files\SubSonic\SubSonic 2.1 Beta 2\SubSonic”

III. Configuring inside Visual Studio 2005/ 2008 to use SubSonic

1. Create new Website project
   
2. Create another new class library project say ‘NorthWindDAL’ and add to solution as shown below (this project is going to act as DAL layer for web project)

3. Add application configuration file to ‘NorthWindDAL’ class library (app.config)
4. Create folder in NorthWindDAL project to keep all Subsonic generated classes
5. Add below configuration sections to app.config file of NorthWindDAL project
   1. Add configsection

<configSections>
                  <section name=“SubSonicService“
                         type=“SubSonic.SubSonicSection,SubSonic“
                         requirePermission=“false“/>

   </configSections> 

2. add Connection strings section

<connectionStrings>
<add name=“NorthWind“               connectionString=“Server=yourserverName;Database=dbName;UID=youruserName;PWD=yourPassword;“/>

   </connectionStrings> 

3. add Subsonic service provider

<SubSonicService defaultProvider=“NorthWind“>
            <providers>
                  <clear/>
                  <add name=“NorthWind“
                         type=“SubSonic.SqlDataProvider, SubSonic“
                         connectionStringName=“NorthWind“
                         generatedNamespace=“NorthWind“  />
            </providers>
   </SubSonicService>

6. Goto Bin folder of NorthWindDAL project and give reference to ‘SubSonic.dll’ available at “Program Files\SubSonic\SubSonic 2.1 Beta 2\SubSonic”
7. and add reference to System.Web and System.Configuration

IV. Adding SubSonic Commander as external tool in Visual studio

Now you are ready for generate code.

When you click on External tool ‘SubSonicDAL’ , it generates code in specified folder that is ‘NorthWind’

That’s it…..  so simple

Serialization & Deserialization:
The process of storing the state of an object to a storage medium. During this process, the public and private fields of the object and the name of the class, are converted to a stream of bytes, which is then written to a data stream. When the object is subsequently deserialized, an exact clone of the original object is created. Serialization/Deserialization is used to transport or to persist objects.

Types of Serialization :
1. Binary Serialization
2. SOAP Serialization
3. XML Serialization
4. Custom Serialization

.NET 3.5 has new object called DataContractJsonSerliaizer used to JSON serialization for Ajax calls / Javascript calls.

Here i am writing JSONHelper class to Serialize and Deserialize
Add Reference: System.Runtime.Serialization.dll(.NET 3.0), System.ServiceModel.Web.dll(.NET 3.5)

using System.Collections.Generic;
using System.Runtime.Serialization;
using System.Runtime.Serialization.Json;
public class JSONHelper
{
    public static string Serialize(T obj)
    {
    DataContractJsonSerializer serializer = new DataContractJsonSerializer(obj.GetType());   
    MemoryStream ms = new MemoryStream();
    serializer.WriteObject(ms, obj);
    string retVal = Encoding.Default.GetString(ms.ToArray());
    return retVal;
    }

    public static T Deserialize(string json)
    {

    T obj = Activator.CreateInstance();
    MemoryStream ms = new MemoryStream(Encoding.Unicode.GetBytes(json));

    DataContractJsonSerializer serializer = new DataContractJsonSerializer(obj.GetType());
    obj = (T)serializer.ReadObject(ms);
    ms.Close();

    return obj;
    }

}

Below class going to use for serialization and Deserialization

[DataContract]
public class Book
{

    private int _id;    private string _name;
    public Book() {}

    public Book(int id, string name)
    {
    _id = id;
    _name = name;
    }

    [DataMember]   
    public int Id
    {
    get { return _id; }

    set { _id = value; }
    }

    [DataMember]

    public string Name
    {
    get { return _name; }

    set { _name = value; }
    }
}

How to Use JSONHelper class to Serialize

Book b1 = new Book(1, “ASP.NET 3.5″);
string jsonOutput = JSONHelper.Serialize<Book>(b1);

Serialization output:
{”Id”:1,”Name”:”ASP.NET 3.5″}

How to Use JSONHelper class to Deserialize
Book b2 = JSONHelper.Deserialize<Book>(jsonOutput);

GO

2. Create table to hold DDL command log data
CREATE TABLE [Audit].[DDLLog](
[id] [int] IDENTITY(1,1) NOT NULL,
[logData] [xml] NOT NULL,
CONSTRAINT [PK_DDLLog] PRIMARY KEY CLUSTERED
([id] ASC)) ON [PRIMARY]
GO

Below Trigger restrict user from Droping tables and Altering tables. If you wanted to do that you must disable trigger first before you proceed to Alter or Drop table.

CREATE TRIGGER Trig_RestrictDropAlterTable

ON DATABASE

FOR DROP_TABLE, ALTER_TABLE

AS

PRINT ‘You must disable Trigger “Trig_RestrictDropAlterTable” to drop or alter tables!’

ROLLBACK

To Disable Trigger
DISABLE TRIGGER [Trig_RestrictDropAlterTable ] ON DATABASE

To provide next level of security from Droping and Altering tables, you can create schema, and give permissions to only one main user on newly created schema. Create this trigger under that schema. So others don’t have permission to disable trigger. So others can’t be able to modify DB structures. Only main users will disable trigger and do nessasary changes in structures.