ViewData: It is of dictionary type, used to store key/value pairs and transmit them between controllers and views.

ViewBag: It is a wrapper built above ViewData, but it is dynamic in nature as appose to ViewData.

TempData: It is also a dictionary type property, but it is only used between subsequent request and is very short lived

While redirecting from one controller, both ViewBag and ViewData properties cannot be used, but TempData property can be used to transport data, as it works for subsequent requests.

And for importing google contacts, firstly we need to download Google Data API and install them to get the required dlls. Then create a web application in Visual Studio, and add those dlls in your bin folder, or add reference of these dlls in your application.

Following dlls are being used for importing address book:

• Google.GData.Client
• Google.GData.Contacts
• Google.GData.Extensions

Now place the required textboxes and button to fetch address book (Two textboxes for username and password, one listbox for address book and one button to start fetching).

following is the code snippet for declaring dll classes in your code behind:

using Google.Contacts;

using Google.GData.Contacts;

using Google.GData.Client;

using Google.GData.Extensions;

following code snippet is to be written behind your button’s click event:

protected void btnAddressBook_Click(object sender, EventArgs e)

{

//Login Information

RequestSettings requestLoginInfo = new RequestSettings(“”, txtEmail.Text, txtPassword.Text);

rsLoginInfo.AutoPaging = true;

// Fetch addressbook and dislay them in ListBox

ContactsRequest conRequest = new ContactsRequest(requestLoginInfo);

Feed <contact> feedContacts = conRequest.GetContacts();

foreach (Contact addressbook in feedContacts.Entries)

{
// Adding contact

lstContacts.Items.Add(addressbook.Title);

foreach (EMail emailId in addressbook.Emails)

{
// Adding Emails for specific contact

lstContacts.Items.Add(” ” + emailId.Address);

}

}

}

Advantages:

• Cost cutting
• More storage for Data.
• Mobilitiy of Data
• Easy Disaster Recovery

Disadvantages

• Implementation of session
• Implementation of authentication
• Migration of existing application

Mostly environment specific config files have different connection strings for development/production environments so when deploying you had to make sure you are applying the correct configuration file.

This problem is solved by visual studio 2010 that allows to build configuration specific config files. In VS 2010, whenever you create a new web application project now, you’ll see that your web.config in your solution explorer actually appears as an expandable node. When you expand it, you will see multiple configuration files for each of your build configurations, that can hold different values for each configuration.

Now when you build your application in a specific build configuration, the correct web.config settings get applied. Similarly when you publish, the correct web.config settings get published.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Net.Sockets;
using System.IO;
using System.Text;
using System.Text.RegularExpressions;
public partial class _Default : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        string domainname = Request.QueryString["domain"].ToString();
        TcpClient objTCPC = new TcpClient();
        objTCPC.Connect("whois.enom.com", 43);
        string strDomain = domainname;// +"\\r\\n";
        byte[] arrDomain = Encoding.ASCII.GetBytes(strDomain);
        Stream objStream = objTCPC.GetStream();
        objStream.Write(arrDomain, 0, strDomain.Length);
        StreamReader objSr = new StreamReader(objTCPC.GetStream(),Encoding.ASCII);
        string strServerResponse = objSr.ReadToEnd();
        strServerResponse = Regex.Replace(strServerResponse, "\n", "<br>");
        Response.Write(strServerResponse);
        objTCPC.Close();
    }
}

string keyWords = “metatags, html, dynamic, generate”;

HtmlMeta keywords = new HtmlMeta();

keywords.Name = “keywords”;

keywords.Content = keyWords;

Page.Header.Controls.Add(keywords);

<%# DateTime.Parse(Eval("DateModified").ToString()).ToString("MM-dd-yyyy")%>

Some more format specifiers that can change format of datetime objects the way it is required.

• through looping techniques to call insert statements for one record at a time.
• Serialize the data in CSV or XML format and send them as a parameter to a stored procedure and then through parsing execute insertion statements.
• generate a file and load them through a SSIS package.
• Use SqlBulkCopy.

SqlBulkCopy is way faster than multiple insert statements, serializing/ deserializing the data, or saving the data out to a file system and running an import.  Its also has no limit on the data you can send across and very efficient in the way it handles inserts.

This is how simple it is to use it. In the example we have a function that writes copies are DataTable into a MS SQL database table called “tblInsertion”.

using System.Data.SqlClient;
…

Function WriteToDB(DataTable dt)

{

SqlBulkCopy sqlBC = new SqlBulkCopy(dbconnectionstring);

sqlBC.BatchSize = 25000;

sqlBC.BulkCopyTimeout = 60;

sqlBC.DestinationTableName = “dbo.tblFooBar” ;

sqlBC.WriteToServer(dt);

}

VS2005 Walkthroughs Crystal Reports

DataSet dsExport = new DataSet();

System.IO.StringWriter tw = new System.IO.StringWriter();

HTMLTextWriter hw = new HTMLTextWriter(tw);

DataGrid dg = new DataGrid();

dg.DataSource = "Dataset to be exported"

hw.WriteLine ("<b><font size=’3′>Exported report</font></b>");

dg.DataBind();

Response.ContentType = "application/vnd.ms-excel";

EnableViewState = false;

Response.Write(tw.ToString());

Response.End();