Send Email through Gmail

System.Web.Mail.MailMessage myMail = new System.Web.Mail.MailMessage(); myMail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpserver", "smtp.gmail.com");
myMail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpserverport", "465");
myMail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/sendusing", "2"); myMail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate", "1");
myMail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/sendusername", "yourid@gmail.com");
myMail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/sendpassword", "gmailpassword");
myMail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpusessl", "true");
myMail.From = "yourid@gmail.com";
myMail.To = "to@gmail.com";
myMail.Subject = "Subject";
myMail.Body = "body";
if (pAttachmentPath.Trim() != "")
{
myMail.Priority = System.Web.Mail.MailPriority.High;
}
System.Web.Mail.SmtpMail.SmtpServer = "smtp.gmail.com:465"; System.Web.Mail.SmtpMail.Send(myMail);

What is an application domain

Previously "PROCESS" where used as security boundaries. One process has its own virtual memory and does not over lap the other process virtual memory; due to this one process can not crash the other process. So any problem or error in one process does not affect the other process. In .NET they went one step ahead introducing application domains. In application domains multiple applications can run in same process with out influencing each other. If one of the application domains throws error it does not affect the other application domains. To invoke method in a object running in different application domain .NET remoting is used.

Static Constructor

Some important point regarding static constructor from C# Language Specification and C# Programmer's Reference :
1) The static constructor for a class executes before any instance of the class is created.

2) The static constructor for a class executes before any of the static members for the class are referenced.

3) The static constructor for a class executes after the static field initializers (if any) for the class.

4) The static constructor for a class executes at most one time during a single program instantiation

5) A static constructor does not take access modifiers or have parameters.

6) A static constructor is called automatically to initialize the class before the first instance is created or any static members are referenced.

7) A static constructor cannot be called directly.

8) The user has no control on when the static constructor is executed in the program.

9) A typical use of static constructors is when the class is using a log file and the constructor is used to write entries to this file.