How to Create Dynamic DropDownLists in ASP.NET

CheapASPNETHostingReview.com | Best and cheap ASP.NET hosting. In this post I will tell you how to create Dynamic DropDownLists in ASP.NET

Object:

Create dropdownlist dynamically with autopostback property true
Keep dropdownlist during postback
Maintain selected value during postback.

Here is the sample for this :

In aspx page:
&lt;form id="form1" runat="server"&gt;
    &lt;div&gt;
        &lt;asp:Table ID="tbl" runat="server"&gt;
        &lt;/asp:Table&gt;
        &lt;asp:Button ID="btnSet" runat="server" Text="Button" onclick="btnSet_Click" /&gt; &lt;/div&gt;
    &lt;/form&gt;

In aspx page:

<div>

<asp:Table ID="tbl" runat="server">

</asp:Table>

<asp:Button ID="btnSet" runat="server" Text="Button" onclick="btnSet_Click" /> </div>

</form>

To Create Dynamic Dropdownlist:

protected void Page_Load(object sender, EventArgs e)
{
    if (!Page.IsPostBack)
    {
    CreateDynamicTable();
    }
}
    private void CreateDynamicTable()
    {  
        // Fetch the number of Rows and Columns for the table
        // using the properties
        int tblRows = 3;
        int tblCols = 3;
        // Now iterate through the table and add your controls
        for (int i = 0; i &lt; tblRows; i++)
        {
            TableRow tr = new TableRow();
            for (int j = 0; j &lt; tblCols; j++)
            {
                TableCell tc = new TableCell();
                DropDownList ddl = new DropDownList();
                ddl.ID = "ddl-" + i.ToString() + "-" + j.ToString();
                for (int k = 0; k &lt; 5; k++)
                {
                    ddl.Items.Add(new ListItem("item-"+k.ToString(),k.ToString())); 
                }
                ddl.AutoPostBack = true;
                ddl.SelectedIndexChanged += new EventHandler(ddl_SelectedIndexChanged);
                // Add the control to the TableCell
                tc.Controls.Add(ddl);
                // Add the TableCell to the TableRow
                tr.Cells.Add(tc);
            }
            // Add the TableRow to the Table
            tbl.Rows.Add(tr);
            tbl.EnableViewState = true;
            ViewState["tbl"] = true;
        }
    }
protected void ddl_SelectedIndexChanged(object sender, EventArgs e)
    {
    // what you want to perform    
    }

protected void Page_Load(object sender, EventArgs e)

{

if (!Page.IsPostBack)

{

CreateDynamicTable();

}

private void CreateDynamicTable()

{

// Fetch the number of Rows and Columns for the table

// using the properties

int tblRows = 3;

int tblCols = 3;

// Now iterate through the table and add your controls

for (int i = 0; i < tblRows; i++)

{

TableRow tr = new TableRow();

for (int j = 0; j < tblCols; j++)

{

TableCell tc = new TableCell();

DropDownList ddl = new DropDownList();

ddl.ID = "ddl-" + i.ToString() + "-" + j.ToString();

for (int k = 0; k < 5; k++)

{

ddl.Items.Add(new ListItem("item-"+k.ToString(),k.ToString()));

}

ddl.AutoPostBack = true;

ddl.SelectedIndexChanged += new EventHandler(ddl_SelectedIndexChanged);

// Add the control to the TableCell

tc.Controls.Add(ddl);

// Add the TableCell to the TableRow

tr.Cells.Add(tc);

}

// Add the TableRow to the Table

tbl.Rows.Add(tr);

tbl.EnableViewState = true;

ViewState["tbl"] = true;

}

protected void ddl_SelectedIndexChanged(object sender, EventArgs e)

{

// what you want to perform

}

To retrieve value on button click:

protected void btnSet_Click(object sender, EventArgs e)
    {
        foreach (TableRow tr in tbl.Controls )
        {
            foreach (TableCell tc in tr.Controls)
           {
                if (tc.Controls[0] is DropDownList)
                {
                    Response.Write(((DropDownList)tc.Controls[0]).SelectedItem.Text+" ");        
                }
            }
            Response.Write("&lt;br/&gt;"); 
        }
    }

protected void btnSet_Click(object sender, EventArgs e)

{

foreach (TableRow tr in tbl.Controls )

{

foreach (TableCell tc in tr.Controls)

{

if (tc.Controls[0] is DropDownList)

{

Response.Write(((DropDownList)tc.Controls[0]).SelectedItem.Text+" ");

}

Response.Write("<br/>");

}

Right Now, No output because dynamic controls are lost in postback then what to do.
So we need to save dynamic controls value and generate dynamic controls again.we need to maintain viewstate.

protected override object SaveViewState()
{
    object[] newViewState = new object[2];
    List&lt;string&gt; txtValues = new List&lt;string&gt;();
    foreach (TableRow row in tbl.Controls)
    {
        foreach (TableCell cell in row.Controls)
        {
            if (cell.Controls[0] is DropDownList)
            {
                txtValues.Add(((DropDownList)cell.Controls[0]).SelectedIndex.ToString());
            }
        }
    }
    newViewState[0] = txtValues.ToArray();
    newViewState[1] = base.SaveViewState();
    return newViewState;
}
protected override void LoadViewState(object savedState)
{
    //if we can identify the custom view state as defined in the override for SaveViewState
    if (savedState is object[] &amp;&amp; ((object[])savedState).Length == 2 &amp;&amp; ((object[])savedState)[0] is string[])
    {
        object[] newViewState = (object[])savedState;
        string[] txtValues = (string[])(newViewState[0]);
        if (txtValues.Length &gt; 0)
        {
            //re-load tables
            CreateDynamicTable();
            int i = 0;
            foreach (TableRow row in tbl.Controls)
            {
                foreach (TableCell cell in row.Controls)
                {
                    if (cell.Controls[0] is DropDownList &amp;&amp; i &lt; txtValues.Length)
                    {
                        ((DropDownList)cell.Controls[0]).SelectedIndex = Convert.ToInt32(txtValues[i++]);
                    }
                }
            }
        }
        //load the ViewState normally
        base.LoadViewState(newViewState[1]);
    }
    else
    {
        base.LoadViewState(savedState);
    }
}

protected override object SaveViewState()

{

object[] newViewState = new object[2];

List<string> txtValues = new List<string>();

foreach (TableRow row in tbl.Controls)

{

foreach (TableCell cell in row.Controls)

{

if (cell.Controls[0] is DropDownList)

{

txtValues.Add(((DropDownList)cell.Controls[0]).SelectedIndex.ToString());

}

newViewState[0] = txtValues.ToArray();

newViewState[1] = base.SaveViewState();

return newViewState;

}

protected override void LoadViewState(object savedState)

{

//if we can identify the custom view state as defined in the override for SaveViewState

if (savedState is object[] && ((object[])savedState).Length == 2 && ((object[])savedState)[0] is string[])

{

object[] newViewState = (object[])savedState;

string[] txtValues = (string[])(newViewState[0]);

if (txtValues.Length > 0)

{

//re-load tables

CreateDynamicTable();

int i = 0;

foreach (TableRow row in tbl.Controls)

{

foreach (TableCell cell in row.Controls)

{

if (cell.Controls[0] is DropDownList && i < txtValues.Length)

{

((DropDownList)cell.Controls[0]).SelectedIndex = Convert.ToInt32(txtValues[i++]);

}

//load the ViewState normally

base.LoadViewState(newViewState[1]);

}

else

{

base.LoadViewState(savedState);

}

How to Backup and Restore Database in ASP.NET

CheapASPNETHostingReview.com | Best and cheap ASP.NET Hosting. Sometimes we need to provide backup and restore facility in ASP.NET application in application’s control panel. In this article, I am going to explain how to develop a database backup and restore application in ASP.NET. I have taken example of SQL Server in this article however, this application can be used to backup and restore any database that .NET supports. You just need to change their provider instead of System.Data.SqlClient and a single SQL Statement to list the table names of the database. I will explain them in details later in this article.

My Backup and Restore web application looks like below:

1. Create a UI for database backup and restore

In this step, let us create a simple UI in ASP.NET to list all the database tables in the ListBox control that let the end user select the table to take backup and restore. Also put two buttons named Backup and Restore to do its respective functionality. My code for above UI looks like below:

<form id="form1" runat="server">
<div>
<table cellpadding="2" cellspacing="1" border="1" style="border-collapse: collapse;">
<tr>
<th style="background-color:#e0e0e0;">
Backup and Restore SQL Server
<br />
database using ASP.NET</th>
</tr> 

<tr>
<td align="Center">
List of Tables</td>
</tr> 

<tr>
<td align="Center">
<asp:ListBox ID="ListBox1" Rows="10" runat="Server" DataTextField="table_name" DataValueField="table_name">
</asp:ListBox>
</td>
</tr> 

<tr>
<td align="Center">
<span onclick="return confirm('Are you sure to backup selected table?')">
<asp:Button ID="btnBackup" runat="Server" Text="Backup" OnClick="BackUpNow" />
</span>
<span onclick="return confirm('Are you sure to restore selected table?')">
<asp:Button ID="btnRestore" runat="Server" Text="Restore" OnClick="RestoreNow" />
</span>
</td>
</tr>
</table> 

<asp:Label ID="lblMessage" runat="Server" EnableViewState="False" ForeColor="Blue"></asp:Label> 

</div>
</form>

<div>

<tr>

Backup and Restore SQL Server

<br />

database using ASP.NET</th>

</tr>

<tr>

List of Tables</td>

</tr>

<tr>

<asp:ListBox ID="ListBox1" Rows="10" runat="Server" DataTextField="table_name" DataValueField="table_name">

</asp:ListBox>

</td>

</tr>

<tr>

<asp:Button ID="btnBackup" runat="Server" Text="Backup" OnClick="BackUpNow" />

</span>

<asp:Button ID="btnRestore" runat="Server" Text="Restore" OnClick="RestoreNow" />

</span>

</td>

</tr>

</table>

<asp:Label ID="lblMessage" runat="Server" EnableViewState="False" ForeColor="Blue"></asp:Label>

</div>

</form>

2. Populate the database table in the ListBox control

In this step, we will write method that will populate all database tables in the ListBox control that will let the end user select the table to perform Backup or Restore. My code looks like below:

string connStr = ConfigurationManager.AppSettings["DatabaseToBackup"].ToString(); 

protected void Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{
PopulateDatabaseTables();
}
}
/// <summary>
/// Populate database tables first
/// </summary>
private void PopulateDatabaseTables()
{
string tableName = string.Empty;
string sql = "SELECT *, name AS table_name " +
" FROM sys.tables WHERE Type = 'U' ORDER BY table_name";
using (SqlConnection conn = new SqlConnection(connStr))
{
using (DataTable table = new DataTable())
{
conn.Open();
using (SqlDataAdapter dAd = new SqlDataAdapter(sql, conn))
{
dAd.Fill(table);
}
ListBox1.DataSource = table;
ListBox1.DataBind();
}
}
}

string connStr = ConfigurationManager.AppSettings["DatabaseToBackup"].ToString();

protected void Page_Load(object sender, EventArgs e)

{

if (!IsPostBack)

{

PopulateDatabaseTables();

}

/// <summary>

/// Populate database tables first

/// </summary>

private void PopulateDatabaseTables()

{

string tableName = string.Empty;

string sql = "SELECT *, name AS table_name " +

" FROM sys.tables WHERE Type = 'U' ORDER BY table_name";

using (SqlConnection conn = new SqlConnection(connStr))

{

using (DataTable table = new DataTable())

{

conn.Open();

using (SqlDataAdapter dAd = new SqlDataAdapter(sql, conn))

{

dAd.Fill(table);

}

ListBox1.DataSource = table;

ListBox1.DataBind();

}

You can notice in the above code snippet, I am calling a method named PopulateDatabaseTables() in the Not IsPostBack condition under Page_Load event that will populate all the tables of the database in the ListBox control. Notice the select statement that has been stored into sql variable. This select statement varies between databases to databases. To list all the tables in SQL Server database, you need to use above select statement. To list all the tables of the MySQL database, you need to write “show tables” in place of above select statement. Of course, you need to change the provider as well to connect to the MySQL database.

3. Code for taking backup of the selected table

In this step, we shall write code to take backup of the selected table when Backup button will be clicked. You can see that in OnClick event of the Backup button, I have specified BackupNow method. Let us see the code for this method.

/// <summary>
/// Backup the selected table
/// </summary>
/// <param name="sender"></param>
/// <param name="e"></param>
protected void BackUpNow(object sender, EventArgs e)
{
string tableName = ListBox1.SelectedValue;
using (DataSet dSetBackup = new DataSet())
{
using (SqlConnection conn = new SqlConnection(connStr))
{
using (SqlDataAdapter dAd = new SqlDataAdapter("select * from " + tableName, conn))
{
dAd.Fill(dSetBackup, tableName);
}
}
dSetBackup.WriteXml(Server.MapPath("~/backup/" + tableName + ".xml"));
lblMessage.Text = "Backup for table <b>" + tableName + "</b> successful!";
}
}

/// <summary>

/// Backup the selected table

/// </summary>

/// <param name="sender"></param>

/// <param name="e"></param>

protected void BackUpNow(object sender, EventArgs e)

{

string tableName = ListBox1.SelectedValue;

using (DataSet dSetBackup = new DataSet())

{

using (SqlConnection conn = new SqlConnection(connStr))

{

using (SqlDataAdapter dAd = new SqlDataAdapter("select * from " + tableName, conn))

{

dAd.Fill(dSetBackup, tableName);

}

dSetBackup.WriteXml(Server.MapPath("~/backup/" + tableName + ".xml"));

lblMessage.Text = "Backup for table <b>" + tableName + "</b> successful!";

}

In the above code snippet, I have got the selected table name form ListBox in the tableName variable. Selected all records from that table and filled into a DataSet named dSetBackup. Later on I used WriteXml method of DataSet to write the contents of the selected table in an xml file. The name of the xml file will be the table name in my case and will be placed in the backup folder. Then I have written a success message. This way your end user will be able to take backup of all the tables in the database.

4. Code for restoring selected table

In this step, we shall see how to restore a selected table into the database once the Restore button will be clicked. Notice the Restore button where I have specified RestoreNow method in the OnClick event. The code for this method looks like below:

/// <summary>
/// Restore the selected table
/// </summary>
/// <param name="sender"></param>
/// <param name="e"></param>
protected void RestoreNow(object sender, EventArgs e)
{
string restoreConnStr =
ConfigurationManager.AppSettings["RestoreConnStr"].ToString();
string tableName = ListBox1.SelectedValue;
using (SqlConnection conn = new SqlConnection(restoreConnStr))
{
using (DataSet dSetBackup = new DataSet())
{
// get the schema of the selected table from the database to restore
using (SqlDataAdapter dAd = new SqlDataAdapter("select * from " + tableName,
conn))
{
     // Following line will get the schema of the selected table in the dSetBackup DataSet
     dAd.Fill(dSetBackup, tableName); 

// get the data for selected table from backed up XML file
using (DataSet dSet = new DataSet())
{
dSet.ReadXml(Server.MapPath("~/backup/" + tableName + ".xml"));
// Loop through all rows of the selected table and add into dSetBackup DataSet
foreach (DataRow row in dSet.Tables[0].Rows)
{
dSetBackup.Tables[0].NewRow();
dSetBackup.Tables[0].Rows.Add(row.ItemArray);
} 

// Create a command builder to update dSetBackup DataSet
SqlCommandBuilder cmd = new SqlCommandBuilder(dAd); 

// Following update command will push all added rows of dSetBackup DataSet into the database
dAd.Update(dSetBackup, tableName); // We are done !!!
}
}
lblMessage.Text = "Restore of table <b>" + tableName + "</b> successful!";
}
}
}

/// <summary>

/// Restore the selected table

/// </summary>

/// <param name="sender"></param>

/// <param name="e"></param>

protected void RestoreNow(object sender, EventArgs e)

{

string restoreConnStr =

ConfigurationManager.AppSettings["RestoreConnStr"].ToString();

string tableName = ListBox1.SelectedValue;

using (SqlConnection conn = new SqlConnection(restoreConnStr))

{

using (DataSet dSetBackup = new DataSet())

{

// get the schema of the selected table from the database to restore

using (SqlDataAdapter dAd = new SqlDataAdapter("select * from " + tableName,

conn))

{

// Following line will get the schema of the selected table in the dSetBackup DataSet

dAd.Fill(dSetBackup, tableName);

// get the data for selected table from backed up XML file

using (DataSet dSet = new DataSet())

{

dSet.ReadXml(Server.MapPath("~/backup/" + tableName + ".xml"));

// Loop through all rows of the selected table and add into dSetBackup DataSet

foreach (DataRow row in dSet.Tables[0].Rows)

{

dSetBackup.Tables[0].NewRow();

dSetBackup.Tables[0].Rows.Add(row.ItemArray);

}

// Create a command builder to update dSetBackup DataSet

SqlCommandBuilder cmd = new SqlCommandBuilder(dAd);

// Following update command will push all added rows of dSetBackup DataSet into the database

dAd.Update(dSetBackup, tableName); // We are done !!!

}

lblMessage.Text = "Restore of table <b>" + tableName + "</b> successful!";

}

Please note that in order to above code snippet work, you must have the schema in place into the Restore database. This schema must match the original database schema from which you had taken backup otherwise your restore will not work.

In the above code snippet, I am first getting the connection string of the database where we need to restore the data. Then I am getting the schema of the selected table into the dSetBackup DataSet using dAd (SqlDataAdapter), as there will not be any row into the restore database, so it will only give the schema of the table. This will help us to push the backed up data into this DataSet. In the next line, I have read the backed up xml of the table using ReadXml method of the DataSet that will get all the backed up data for that table into the dSet DataSet. In next line, I am looping through every rows of the dSet DataSet table and adding them into our dSetBackup DataSet. Next, I have created a SqlCommandBuilder object for the SqlDataAdapter. This will internally build insert, update, delete statement for the dSetBackup DataTable. In the following line, I have used dAd.Update (SqlDataAdapter update method) to push the data into the restore database. At last I am writing the success message. Simple! Isn’t it?

Save

Tips to Choose The Best and Cheap ASP.NET Hosting Company

CheapASPNETHostingReview.com | Best and Cheap ASPNET Hosting. In this post I will explains tips to choose the best and Cheap ASP.NET hosting companies.

Best OFFER Cheap ASP.NET Hosting Get it NOW !!

How To choose the best and cheap ASP.NET hosting

How To choose the best and cheap ASP.NET hosting company, there are hundreds of web hosting company on the internet and choosing any one of them for your ASP.NET hosting needs can be quite difficult, you need to select a hosting company with best hosting plan that support for your bussines needs rather than creating roadblocks for your succes. The right plans means the ideal feature along with the required capacities. Afforability is also an important factor, but it should not come at the cost of quality service and features, so how to choose the right ASP.NET hosting plan and provider to meet your needs

In this post I would like to give you tips how to choose the best asp.net hosting company for your business. When you plan to run a blog, manage photos, host apps and much more, the first thing you need to do is looking for a good web hosting company. A good web host offers you the tools, bandwidth, and storage you need. Besides, it should also provide technical support for you to solve some issues. To choose a good web hosting company, you need to consider the following tips :

Choosing The Best and Cheap ASP.NET Hosting Company

<strong>Features</strong>

The feature of the web hosting service is also important. A good web hosting company should provide enough server resources to customers, including disk space, band width, databases, hosted domains, etc. Meanwhile, multiple scripting languages should be supported. Some important features that a good web hosting company should have are listed as below Plesk panel is another critical factor you should take into consideration. A good control panel can help you all manage hosting accounts, including files, databases, websites, email accounts, domains and so on. Many web hosting companies including ASPHostPortal.com are favor of Plesk panel, which is well known for its user-friendly interface and comprehensive tools. Additionally, some web hosting companies provide one-click installer to help users install the applications in a simple way.

<strong>Price</strong>

Before knowing other aspects of a web host, the first thing you should take into consideration is the price of a web hosting service. It is necessary to have a basic understanding about the regular price, discounted price or discounts of the web hosting service, which help you choose the most affordable one to run the business. Generally, web hosts price shared web hosting under $10/mo, such as the ASPHostPortal ASP.NET hosting is starting at $5.00/mo with free domain and double SQL space promotionally. In addition, some web hosts offer advertising credits or free domains to their customers, which is also a good method to save money.

<strong>Uptime & Speed</strong>

Every web host promise to offer 99% uptime guarantee, but only a few of them achieve the guarantee in practice. A good web hosting company should utilize high performance servers to ensure reliable and secure hosting environment, which barely has unplanned downtime issues. Besides, a 24×7 server monitoring should be available. Hosting speed determines how fast you web pages are loaded. A good web host can provide a fast hosting environment and ensure that their data can be transferred at a high speed. And also, a 24×7 server monitoring is essential to address their issues promptly.

<strong>Technical Support</strong>

When choosing a web hosting company, you need to consider whether it offers a customer support. A good web host should allow customers contact the professional support team via various communication channels, such as live chat, and email, which are available 24 hours a day, 7 days a week to make sure customers can have an immediate solution to their issues. Besides, many online resources should be available to customers, including knowledgebase, forum, ticket system, tutorials, and much more, which ensure customers have a better hosting environment.

<strong>Customer Satisfaction Rate</strong>

Generally, good web hosting companies always have high reputation in community and high customer satisfaction rate among customers. To have a better understanding about the company, you require browsing a large amount of customer reviews to know whether the customers are satisfied the company. You should choose a company which has a favorable reception among customers.

NOTE :” On the basis of the tips above, you can charge what kind of web hosting company is suitable for running your business. After a comprehensive consideration, you should choose a company which provides you excellent service, affordable price, professional support and acquire a good reputation among customers. With guidance like this article, you’re able to start your own business right now”.

Cheap ASP.NET Hosting Tutorial – ASP.NET VS Classic ASP.NET

Cheap Classic ASP.NET Hosting Recommendation

ASPHostPortal

^$1.00

Host Intro

/mo

Host 1 Site

1 GB Disk Space

10 GB Bandwidth

0 SQL Server db

SQL Server 2008/2012/2014

0 MB SQL Server / db

0 MySQL db

0 MB MySQL /db

50 MB Email Space

ASPHostPortal

^$5.00

Host One

/mo

Host Unlimited Sites

5 GB Disk Space

60 GB Bandwidth

2 SQL Server db

SQL Server 2008/2012/2014

200 MB SQL /db

3 MySQL db

200 MB MySQL /db

200 MB Email Space

ASPHostPortal

^$9.00

Host Two

/mo

Host Unlimited Sites

15 GB Disk Space

150 GB Bandwidth

4 SQL Server db

SQL Server 2008/2012/2014

500 MB SQL / db

6 MySQL db

500 MB MySQL /db

500 MB Email Space

ASPHostPortal

^$14.00

Host Three

/mo

Host Unlimited Sites

50 GB Disk Space

500 GB Bandwidth

6 SQL Server db

SQL Server 2008/2012/2014

1000 MB SQL / db

10 MySQL db

1000 MB MySQL /db

1000 MB Email Space

ASP.NET VS Classic ASP.NET

CheapASPNETHostingReview.com | Best and cheap ASP.NET Hosting. Today In this post I will explains the difference between the Classic ASP and ASP.Net and also focuses on the new features in ASP.NET. Let’s discuss the differences between these two in detail:

Process Isolation

ASP is running under the inetinfo.exe (IIS) process space and hence susceptible to application crashes due to that the IIS needs to be stopped or restarted. ASP is related to the process isolation setting in IIS. Where as, ASP.Net process is separate from inetinfo.exe (IIS process). Though the entry point into a ASP.Net application is still IIS but it is not related to the IIS process isolation settings.

Non-MS Platform Support

Classical ASP has no mechanism of running itself on non- Microsoft technology platforms like the “The Apache Web Server” (there are some third party products, like ChiliSoft) but, ASP.NET could be run on non- Microsoft Platforms also. Cassini is a sample Web server produced by Microsoft which, among other projects, has been used to host ASP.NET with Apache.

Multi Language Support in WebPage

Only VBScript and Javascript were available for scripting in ASP where as, in ASP.NET there are no such restrictions. The .NET compliant language can be used with ASP.NET including several like C# and VB.NET, where both of them are server-sided languages.

Interpretation Vs Compilation

In ASP, an interpreter like Jscript or VBScript is used to execute the server-side code. When an ASP page is requested, the text of that page is parsed linearly. The content that is not server-side script is passed back as it is to the response. Where as, the server-side script in the page is executed through the appropriate interpreter, and the output is then submitted back to the response. The efficiency of page rendering is affected by this architecture in several ways. Firstly, on the go interpreting of the server-side script. A common optimization for the ASP applications for this side affect is to move a mass of server-side script into precompiled COM components to improve the response time. Secondly, the intermingling server-side evaluation blocks with static HTML is another efficiency concern. It is less efficient than the evaluating a single server-side blocks because the interpreter has to be invoked time and again.

As a rescue, many ASP developers resort to large blocks of server-side script for replacing static HTML elements with Response.Write() invocations instead. Eventually, this ASP model permits the inclusion of different blocks of scripts within a page to be written in different script languages. This may appeal in some ways but it also reduces performance by requiring that a particular page load both scripting engines to process a request that consumes more time and memory if compared to just using one language.

But in ASP.NET, the pages are always compiled into .Net classes housed within assemblies. This class includes both the server-side code and static HTML, so when the page is accessed for the first time, subsequent rendering of that page is serviced by executing the compiled code. All the inefficiencies of the scripting model of traditional ASP are eliminated by this. No longer had any performance difference between compiled components and server-side code embedded within a page observed. Both of them are compiled assemblies now. Also, no performance difference between interspersing server-side code blocks among static HTML elements and writing large blocks of server side code and using Response.Write() for static HTML content. The .aspx file is parsed into a single code file and compiled, its not possible to use multiple

This eliminates all the inefficiencies of the scripting model of traditional ASP. There is no longer any performance difference between compiled components and server-side code embedded within a page they are now both compiled components. There is also no performance difference between interspersing server-side code blocks among static HTML elements, and writing large blocks of server-side code and using Response.Write() for static HTML content. Also, because the .aspx file is parsed into a single code file and compiled, it is not possible to use multiple server-side languages within a single .aspx file.

Debugging benefits

In classic ASP, debugging is a tough task because of limited support due to the interpreted model. In contrast, not only ASP.NET improves the performance over the interpreted model but also provides debugging tools for component developers and pages compiled into classes. The page errors are generated as compiled errors and there is a fir chance that most of them will be discovered at the compilation time instead of runtime due to the fact that VB.Net and C# are strongly typed languages. In addition to this, the tools available to the Windows Forms .Net developer are applicable to the ASP.NET developer.

Server-Side code placement Web Page

In ASP pages you might include the executable code outside the scope of a function within a script block marked as “runat=server” and you may also define a function within a pair of server side script tags. Where as in ASP.Net the former is no longer supported and the latter is also not possible.

A default constructor is provided by the generated class definition, and it would be a compiler error if you try to write a default constructor. For this, you can choose the alternative method of separating the layout from the page logic which consequently gives you a complete control over the class definition. This method is called code-behind.

Deployment Strategies

The components used by pages and deployed in this manner were difficult to update or replace in the Classic ASP. You are required to shutdown the IIS because of the fact that while the application was functioning, it referred to the component file for replacement. So, after taking your web server temporarily offline, you had to replace the file and then restart IIS. But, in ASP.NET it aimed to get rid of the need to stop the functioning Web application whenever the components needed to be updated or replaced.

To attain this, the designers of ASP.NET had to ensure two things: first, that the running application not hold a reference to the component file and second, that whenever the component file was replaced with a new version, that new version was picked up with any subsequent requests made to the application. Both of these goals are achieved by using the shadow copy mechanism provided by the Common Language Runtime (CLR).

New Page Directives

In ASP, the directives are required to be placed on the first line of a page within the same delimiting block. For instance:

<%LANGUAGE="VBSCRIPT" CODEPAGE="932"%>

1	<%LANGUAGE="VBSCRIPT" CODEPAGE="932"%>

While ASP.NET required you to place the Language directive with a Page directive, as follows:

<%@Page Language="VB" CodePage="932"%> <%@QutputCache Duration="60" VaryByParam="none" %>

1	<%@Page Language="VB" CodePage="932"%> <%@QutputCache Duration="60" VaryByParam="none" %>

It could be more than one directive lines, which depends on your need. The standard practice is to place the directives in the beginning of the file but you can place it anywhere in your .aspx file.

Threading Issues

The threading model of COM object created using VB within a web-based application is STA (Single Threaded Apartment). ASP worker thread resides in its own STA and hence the compatibility is fine in this case with a little performance hit.

But in ASP.NET, threading model is the Multiple Threaded Apartment (MTA). This means that components that you are using were created for the Single Threaded Apartment (STA) will no longer perform or function reliably without taking some extra precautions in ASP.NET. This includes, but is not limited to, all COM components that have been created using Visual Basic 6.0 and earlier versions. You will be glad to hear that you can still use these STA components without having to change any code. What you need to do is include the compatibility attribute aspcompat=true in a <%@Page> tag on the ASP.NET page. For example, <%@Page aspcompat=true Language=VB%>. Using this attribute will force your page to execute in STA mode, thus ensuring your component will continue to function correctly. If you attempt to use an STA component without specifying this tag, the run time will throw an exception. Setting this attribute to true will also allow your page to call COM+ 1.0 components that require access to the unmanaged ASP built-in objects. These are accessible via the ObjectContext object. If you set this tag to true, your performance will degrade slightly.

Validation & Browser scripting capabilities

There is no inbuilt facility for the validation of controls in the Classic ASP. For example, checking whether a textbox is left blank, or a combo is selected or not, or if a phone number does not fit a particular pattern for area etc.
These kinds of validations required the user to write the client side Javascript code.
It was not less than a headache for the developer to cater the client and server side validations.
What added to the burden on the developer was the Javascript code to fit a particular Browser. Specific code had to be written to fit a set of browsers and it consumed a lot of time.

But in ASP.NET, In built validation controls are provided which are easy to implement and the developer has to worry the least.

The features provided by ASP.NET validation controls:

Browser Independent coding: Developer does not have to worry about the browser and how controls would render to.
Client-Side or Server-Side: The Validation Controls manage the code checking if the client side code is disabled the validation is done on the server side.

Rich Validation set

There are few types of validation which cater to the needs of the validation requirements:

RequiredFieldValidation Control – Requires that the control not be left blank.
CompareValidator Control – Used to compare Data in Two Controls
RangeValidator Control – Used to check for Range validation (also supports various data Types – Date, string etc…)
RegularExpressionValidator Control – Used to check the complicated patterns in the user input.

CustomValidator Control – The final control we have included in ASP.NET is one that adds great flexibility to our validation abilities. We have a custom validator where we get to write out own functions and pass the control value to this function.

This control also provides Client side and server side validation of which the Server side validation could be a different function altogether.

Validation Summary

The validation summary control will collect all the error messages of all the non-valid controls and put them in a tidy list. The list can be either shown on the web page (as shown in the example above) or with a popup box.

Conclusion

Classic ASP goes a long way toward simplifying Web programming. It is demanding when it comes to writing a new DDL from the very beginning as compared with the easier task to write some HTML and mingle it with a script. But then Classic ASP is not fee of issues. The ASP pages are mass of unstructured code. It can be compared to the early days of BASIC programming, where achieving a task quickly was possible but the resultant code was often hard to follow. The object model of ASP has multiple inherent or global objects. For instance, for the generation of the content of an HTTP request, script code is written and the content is send to the client using the intrinsic Response object. In the guaranteed situations where only one client is involved in talking to your Web application, this isn’t much of a problem. But not many web applications guarantee this. And the reason for this is the way ASP is organized by these intrinsic objects.

ASP.Net improves the classic ASP. The same intrinsic objects still remain in ASP.Net and the scripting can be added anywhere on the page per you requirement. In fact, ASP.NET easily manages and runs most of the ASP pages with .aspx extension.

ASP.Net introduces a lot of new features. Like all the components within .Net, ASP.Net pages too are compiled into the assemblies, which give a performance and security edge. Further, it supports the usage of any .Net language. This means there is no restriction over the use of JavaScript or VB Script on your Web pages. Now, you have an option to use more structured languages.

ASP.Net opens up a whole new programming model with the blend and combination of Web forms, server-side controls, data binding, and Web services.

Simpan

Cheap ASP.NET Core 1.0 Hosting Tutorial – 10 Tips You Should Know while Choosing ASP.NET Hosting

CheapASPNETHostingReview.com | Best and cheap ASP.NET hosting. In this post we would like to show you the top 10 tips on choosing ASP.NET hosting providers before starting with our topic.

Being devoted into ASP.NET development and ASP.NET website hosting for a couple of years, we know the secrets hidden in the ASP.NET hosting advertisement and how difficult to find a trusted and cost effective ASP.NET hosting provider.

MS SQL Server database edition and limitation. The latest version of MSSQL 2012 are preferred.
.NET Framework versions. Does it support the version used for your website?
ASP.NET MVC versions. Does it support the version used for your website if you’re using ASP.NET MVC technology?
Does it provide the dedicated application pool so that you won’t be affected by your neighbors?
How long the IIS is set to recycle your website – usually 30 minutes at least is required.
What’s the maximum dedicated memory allowed for the ASP.NET websites?
The hosting provider needs to have the rich experiences and knowledge of how to ensure the high-quality ASP.NET hosting. Besides, it is great that they have got plenty of positive feedbacks from real customers and have been trusted and recommended by a lot of authorities, communities and hosting review sites.
The ASP.NET hosting needs to ensure a high level of hosting reliability with at least 99.9% uptime. Note that this can be achieved with the utilization of cutting-edge data centers, solid server machines and no overselling practice. In addition, some confident web hosts even claim to give you some compensations if they fail to meet their promised uptime track record.
The hosting speed is also pretty essential. After all, your readers can be frustrating if they find it takes a long time for accessing your website. In this case, you need to figure out that whether your web host can ensure the peak performance with no more than 3 seconds for page loading and 400 ms for the server response.
The web host needs to ensure the all-time-rounded technical support to assist you 24 hours a day and 7 days a week. Also, their support staffs need to have the rich knowledge about ASP.NET hosting and related applications.

General Knowledge about ASP.NET

ASP.NET is the server-side online application framework coming with the open source nature. It is designed with the purpose of web development and dynamic webpages production mainly. In addition, developed by Microsoft, ASP.NET has been used by a lot of programmers for the creation of complicated websites, online applications and add-on services.
In fact, ASP.NET has been released since January 2002, which is the successor to the Active Server Pages technology of Microsoft. As it is built based on the Common Language Runtime, developers and programmers can write the ASP.NET code with the help of .NET language.

MOST HIGHLY RECOMMENDED ” We highly recommended ASPHostPortal to host your ASP.NET Core 1.0 hosting. ASPHostPortal.com is offer reliable and affordable windows ASP.NET hosting service, they have four plans, Host Intro, Host one , Host Two anda Host Three. The price starting from $1.00/mo – $14.00/mo. You can buying ASPHostPortal Windows ASP.NET Core 1.0 hosting plan for as low as $1.00/month also you can get FREE Cloud Hosting click here

Simpan

Cheap ASP.NET Hosting Tutorial – Security in ASP.NET 5 and ASP.NET MVC Hosting

Web sites are unfortunately prone to security risks. And so are any networks to which web servers are connected. Setting aside risks created by employee use or misuse of network resources, your web server and the site it hosts present your most serious sources of security risk.

ASP.NET is an open-source server-sideweb application framework designed for web development to produce dynamic web pages. It was developed by Microsoft to allow programmers to build dynamic web sites, web applications and web services.

CheapASPNETHostingreview.com | Cheap and reliable ASP.NET hosting. To make things worse, ASP.NET and MVC traditionally had not much more built-in to offer than boring role checks. This lead to either unmaintainable code (hard coded role names and Authorize attributes) or complete custom implementations – or both.

In ASP.NET 5, a brand new authorization API is supposed to improve that situation – and IMHO – oh yes it does. Let’s have a look.

Overview

ASP.NET 5 supports two styles of authorization out of the box – policy-based and resource-based. Both styles are a substantial improvement over the current ASP.NET authorization features and reduce the need to write your own authorization attribute/filter/infrastructure – though this is still totally possible.

**The new Authorize Attribute**

My main gripe with the old attribute is that it pushes developers towards hard-coding roles (or even worse – names) into their controller code. It violates separation of concerns and leads to hard to maintain code with roles names sprinkled all over your code base.

Also – let’s face it – declarative, role-based security might be nice for demos but is nowhere near flexible enough to write anything but trivial applications.

The new Authorize attribute can still do role checks like this :

[Authorize(Roles = "Sales")]
public IActionResult DoSalesyStuff()
{ /* .. */ }

[Authorize(Roles = "Sales")]

public IActionResult DoSalesyStuff()

{ /* .. */ }

But this is mainly for backwards compatibility (the ability to check for names is gone). The more recommended pattern is to use so called authorization policies instead:

[Authorize("SalesOnly")]
public IActionResult DoSalesyStuff()
{ /* .. */ }

[Authorize("SalesOnly")]

public IActionResult DoSalesyStuff()

{ /* .. */ }

Let’s have a look at policies next.

Policies & Requirements

Policies are a way to create re-usable authorization logic. Policies consist of one or more so called requirements. If all requirements of a policy are met, the authorization check is successful – otherwise it fails.

Policies are created using a policy builder, and the following snippet creates a very simple policy (aka “require authenticated users”) and sets that globally in MVC :

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        // only allow authenticated users
        var defaultPolicy = new AuthorizationPolicyBuilder()
            .RequireAuthenticatedUser()
            .Build();
 
        services.AddMvc(setup =>
        {
            setup.Filters.Add(new AuthorizeFilter(defaultPolicy));
        });
    }
}

public class Startup

{

public void ConfigureServices(IServiceCollection services)

{

// only allow authenticated users

var defaultPolicy = new AuthorizationPolicyBuilder()

.RequireAuthenticatedUser()

.Build();

services.AddMvc(setup =>

{

setup.Filters.Add(new AuthorizeFilter(defaultPolicy));

});

}

There are more extension methods similar to RequireAuthenticatedUser – e.g. RequireClaim or RequireRole.

Another common use case are named policies which can be referenced like the above SalesOnly example (again in Startup.ConfigureServices):

services.AddAuthorization(options =>
{
    // inline policies
    options.AddPolicy("SalesOnly", policy =>
    {
        policy.RequireClaim("department", "sales");
    });
    options.AddPolicy("SalesSenior", policy =>
    {
        policy.RequireClaim("department", "sales");
        policy.RequireClaim("status", "senior");
    });
});

services.AddAuthorization(options =>

{

// inline policies

options.AddPolicy("SalesOnly", policy =>

{

policy.RequireClaim("department", "sales");

});

options.AddPolicy("SalesSenior", policy =>

{

policy.RequireClaim("department", "sales");

policy.RequireClaim("status", "senior");

});

You can also encapsulate requirements in classes, e.g.:

public class StatusRequirement : AuthorizationHandler<StatusRequirement>, IAuthorizationRequirement
{
    private readonly string _status;
    private readonly string _department;
 
    public StatusRequirement(string department, string status, bool isSupervisorAllowed = true)
    {
        _department = department;
        _status = status;
    }
 
    protected override void Handle(AuthorizationContext context, StatusRequirement requirement)
    {
        if (context.User.IsInRole("supervisor"))
        {
            context.Succeed(requirement);
            return;
        }
 
        if (context.User.HasClaim("department", _department) &&
            context.User.HasClaim("status", _status))
        {
            context.Succeed(requirement);
        }
    }
}

public class StatusRequirement : AuthorizationHandler<StatusRequirement>, IAuthorizationRequirement

{

private readonly string _status;

private readonly string _department;

public StatusRequirement(string department, string status, bool isSupervisorAllowed = true)

{

_department = department;

_status = status;

}

protected override void Handle(AuthorizationContext context, StatusRequirement requirement)

{

if (context.User.IsInRole("supervisor"))

{

context.Succeed(requirement);

return;

}

if (context.User.HasClaim("department", _department) &&

context.User.HasClaim("status", _status))

{

context.Succeed(requirement);

}

Which can then be added like this:

options.AddPolicy("DevInterns", policy =>
{
    policy.AddRequirements(new StatusRequirement("development", "intern"));
 
    // ..or using an extension method
    //policy.RequireStatus("development", "intern");
});

options.AddPolicy("DevInterns", policy =>

{

policy.AddRequirements(new StatusRequirement("development", "intern"));

// ..or using an extension method

//policy.RequireStatus("development", "intern");

});

Under the covers, the AddAuthorization extension method also puts an IAuthorizationService (or more specifically the DefaultAuthorizationService) into the DI container. This class can be used to programmatically evaluate policies (amongst other things – more on that later).

To make the authorization service available – simply add it to e.g. a controller constructor:

public class TestController : Controller
{
    private readonly IAuthorizationService _authz;
 
    public TestController(IAuthorizationService authz)
    {
        _authz = authz;
    }
}

public class TestController : Controller

{

private readonly IAuthorizationService _authz;

public TestController(IAuthorizationService authz)

{

_authz = authz;

}

and then use it in an action:

public async Task<IActionResult> SalesSeniorImperative()
{
    if (await _authz.AuthorizeAsync(User, "SalesSenior"))
    {
        return View("success");
    }
    return new ChallengeResult();
}

public async Task<IActionResult> SalesSeniorImperative()

{

if (await _authz.AuthorizeAsync(User, "SalesSenior"))

{

return View("success");

}

return new ChallengeResult();

}

Remark ChallengeResult can be used to trigger an “access denied” condition in MVC. The cookie middleware e.g. will translate that either into a redirect to a login page for anonymous users, or a redirect to an access denied page for authenticated users.

Remark 2 Since views in MVC 6 also support DI, you can inject the authorization service there as well. Some people like this approach to conditionally render UI elements.

@{
    ViewData["Title"] = "Home Page";
    
    @using Microsoft.AspNet.Authorization
    @inject IAuthorizationService _authz
}
 
@if (await _authz.AuthorizeAsync(User, "SalesOnly"))
{
    <div>
        <a href="test/salesOnly">Sales only</a>
    </div>
}

ViewData["Title"] = "Home Page";

@using Microsoft.AspNet.Authorization

@inject IAuthorizationService _authz

}

@if (await _authz.AuthorizeAsync(User, "SalesOnly"))

{

<div>

<a href="test/salesOnly">Sales only</a>

</div>

}

This is a nice way to centralize authorization policies and re-use them throughout the application.

The only thing I don’t like about this approach is, that it pushes you towards using the claims collection as the sole data source for authorization decisions. As we all know, claims describe the identity of the user, and are not a general purpose dumping ground for all sorts of data – e.g. permissions.

It would be nice if one could use the DI system of ASP.NET to make further data source accessible in custom requirement. I’ve opened an issue for that – we’ll see what happens.

Resource-based Authorization

This is a new approach for ASP.NET and is inspired by the resource/action based approach that we had in WIF before (which was ultimately inspired by XACML). We also like that approach a lot, but the problem with the WIF implementation (and also ours) was always that due to the lack of strong typing, the implementation became messy quickly (or at least you needed a certain amount of discipline to keep it clean over multiple iterations).

The idea is simple – you identify resources that your application is dealing with – e.g. customers, orders, products (yawn). Then you write a so called handler for each of these resources where you express the authorization requirements in code.

You use requirements to express whatever action is supposed to be applied to the resource, and conclude with a success/failure, e.g.:

public class CustomerAuthorizationHandler : 
    AuthorizationHandler<OperationAuthorizationRequirement, Customer>
{
    protected override void Handle(AuthorizationContext context, 
        OperationAuthorizationRequirement requirement, 
        Customer resource)
    {
        // implement authorization policy for customer resource
    }
}

public class CustomerAuthorizationHandler :

AuthorizationHandler<OperationAuthorizationRequirement, Customer>

{

protected override void Handle(AuthorizationContext context,

OperationAuthorizationRequirement requirement,

Customer resource)

{

// implement authorization policy for customer resource

}

Operation requirements are built-in and can be used to model simple string-based actions – but you can also write your own, or derive from OperationAuthorizationRequirement.

public static class CustomerOperations
{
    public static OperationAuthorizationRequirement Manage = 
        new OperationAuthorizationRequirement { Name = "Manage" };
    public static OperationAuthorizationRequirement SendMail =
        new OperationAuthorizationRequirement { Name = "SendMail" };
 
    public static OperationAuthorizationRequirement GiveDiscount(int amount)
    {
        return new DiscountOperationAuthorizationRequirement
        {
            Name = "GiveDiscount",
            Amount = amount
        };
    }
}

public static class CustomerOperations

{

public static OperationAuthorizationRequirement Manage =

new OperationAuthorizationRequirement { Name = "Manage" };

public static OperationAuthorizationRequirement SendMail =

new OperationAuthorizationRequirement { Name = "SendMail" };

public static OperationAuthorizationRequirement GiveDiscount(int amount)

{

return new DiscountOperationAuthorizationRequirement

{

Name = "GiveDiscount",

Amount = amount

};

}

You then register the resource handler with the DI system and can access it imperatively from within your controllers (using the above mentioned authorization service):

public async Task<IActionResult> Discount(int amount)
{
    var customer = new Customer
    {
        Name = "Acme Corp",
        Region = "south",
        Fortune500 = true
    };
 
    if (await _authz.AuthorizeAsync(User, customer, 
        CustomerOperations.GiveDiscount(amount)))
    {
        return View("success");
    }
            
    return new ChallengeResult();
}

public async Task<IActionResult> Discount(int amount)

{

var customer = new Customer

{

Name = "Acme Corp",

Region = "south",

Fortune500 = true

};

if (await _authz.AuthorizeAsync(User, customer,

CustomerOperations.GiveDiscount(amount)))

{

return View("success");

}

return new ChallengeResult();

}

What I like about this approach is that the authorization policy has full strong typed access to the domain object it implements authorization for, as well as the principal. This is a huge improvement over the WIF API. It also makes it easy to unit test your controller without the authorization code – and even more importantly (at least for security guy) – it allows unit testing the authorization policy itself.

protected override void Handle(AuthorizationContext context, 
    OperationAuthorizationRequirement requirement, 
    Customer resource)
{
    // user must be in sales
    if (!context.User.HasClaim("department", "sales"))
    {
        context.Fail();
        return;
    }
 
    // ...and responsible for customer region
    if (!context.User.HasClaim("region", resource.Region))
    {
        context.Fail();
        return;
    }
 
    // if customer is fortune 500 - sales rep must be senior
    if (resource.Fortune500)
    {
        if (!context.User.HasClaim("status", "senior"))
        {
            context.Fail();
            return;
        }
    }
 
    if (requirement.Name == "GiveDiscount")
    {
        HandleDiscountOperation(context, requirement, resource);
        return;
    }
 
    context.Succeed(requirement);
}

protected override void Handle(AuthorizationContext context,

OperationAuthorizationRequirement requirement,

Customer resource)

{

// user must be in sales

if (!context.User.HasClaim("department", "sales"))

{

context.Fail();

return;

}

// ...and responsible for customer region

if (!context.User.HasClaim("region", resource.Region))

{

context.Fail();

return;

}

// if customer is fortune 500 - sales rep must be senior

if (resource.Fortune500)

{

if (!context.User.HasClaim("status", "senior"))

{

context.Fail();

return;

}

if (requirement.Name == "GiveDiscount")

{

HandleDiscountOperation(context, requirement, resource);

return;

}

context.Succeed(requirement);

}

In addition, the resource handler can make full use of the DI system. That means we can inject access to arbitrary data stores. A very common use case is to use some sort of database to query permission tables or similar. This makes it very flexible.

Imagine a permission service that queries your authorization using some backing store (the _permissions variable):

private void HandleDiscountOperation(
    AuthorizationContext context, 
    OperationAuthorizationRequirement requirement, 
    Customer resource)
{
    var discountOperation = requirement as DiscountOperationAuthorizationRequirement;
    var salesRep = context.User.FindFirst("sub").Value;
 
    var result = _permissions.IsDiscountAllowed(
        salesRep,
        resource.Id,
        discountOperation.Amount);
 
    if (result)
    {
        context.Succeed(requirement);
    }
    else
    {
        context.Fail();
    }
}

private void HandleDiscountOperation(

AuthorizationContext context,

OperationAuthorizationRequirement requirement,

Customer resource)

{

var discountOperation = requirement as DiscountOperationAuthorizationRequirement;

var salesRep = context.User.FindFirst("sub").Value;

var result = _permissions.IsDiscountAllowed(

salesRep,

resource.Id,

discountOperation.Amount);

if (result)

{

context.Succeed(requirement);

}

else

{

context.Fail();

}

All in all – I am very pleased with this new API and it will be interesting to see how it performs in a real application. Happy coding 🙂

Cheap ASP.NET Security With SQL Server 2005

CheapASPNETHostingRerview.com | Cheap and Reliable ASP.NET hosting. This article focuses on security concerm when using SQL Server 2005 in ASP.NET application..

Today I was trying to access the web page from and getting following error
Error Message:Login failed for user . The user is not associated with a trusted SQL Server connection.Web server and database are on different server and I am using Virtual machines (VMWare) for my development and DB server.There can be problem in SQL server or IIS or application, so lets start with SQL Server.SQL Server Settings: The security should be set for SQL Server and Windows Authentication.

The SQL server has the logins for authenticated users and has proper permissions as I also use development machine to maintain DB.

IIS: Open IIS and select properties and under directory security tab click edit button.

Uncheck Anonymous access and check integrated windows security; integrated windows security will enable users login to be used for authentication instead of IIS default user.

Now, lets put application web.config under microscope.
I have custom error tag to redirect error to default page

<customErrors mode="On" defaultRedirect="showError.aspx">
</customErrors>

1 2	<customErrors mode="On" defaultRedirect="showError.aspx"> </customErrors>

This is good and for testing I set the Mode tag to off
Connection string uses integrated security tag and set it to true.

"server=servername;database=TestDB;Integrated Security=true" />

1	"server=servername;database=TestDB;Integrated Security=true" />

Here is another tag identity. Ah! Impersonate is false and I want it false so I can have connection pooling.

<identity impersonate="false"/>

1	<identity impersonate="false"/>

So where is the problem, all the setting seems right, why the heck it does not work.
I changes the identity impersonate tag to true and Voila! It works.J
For the time being I can work but it’s not a solution. L Adding a login to SQL Server for IIS user of web server is also not going to work.

Cheap ASP.NET Hosting Review – How To Choose The Best and Cheap ASP.NET Hosting Company

CheapASPNETHostingReview.com | Cheap ASP.NET hosting Review. How To choose the best and cheap ASP.NET hosting company, there are hundreds of web hosting company on the internet and choosing any one of them for your ASP.NET hosting needs can be quite difficult, you need to select a hosting company with best hosting plan that support for your bussines needs rather than creating roadblocks for your succes. The right plans means the ideal feature along with the required capacities. Afforability is also an important factor, but it should not come at the cost of quality service and features, so how to choose the right ASP.NET hosting plan and provider to meet your needs

Choosing The Best and Cheap ASP.NET Hosting Company

Features

Price

Uptime & Speed

Technical Support

Customer Satisfaction Rate

NOTE :” On the basis of the tips above, you can charge what kind of web hosting company is suitable for running your business. After a comprehensive consideration, you should choose a company which provides you excellent service, affordable price, professional support and acquire a good reputation among customers. With guidance like this article, you’re able to start your own business right now”.