There are certain scenarios where Textbox webcontrols will not post the Text value enter by the user back to the server. To understand these scenarios I created the following form consisting of 4 textboxes. On the first textbox (ReadOnlyTextBox) I set the ReadOnly property to true using the properties window. On the second textbox (DisabledTextBox) I set the enabled property to false using the properties window. On the next two textboxes I did not set the ReadOnly or Eanbled properties, but I did add attributes via C# code in the Form_Load event as will be highlighted later. Here is the complete form.

 
<p>
    <asp:TextBox ID="ReadOnlyTextBox" ClientIDMode="Static" runat="server" ReadOnly="True"></asp:TextBox>
</p>
<p>
    <asp:TextBox ID="DisabledTextBox" ClientIDMode="Static" runat="server" Enabled="False"></asp:TextBox>
</p>
<p>
    <asp:TextBox ID="ReadOnlyByAttributeTextBox" ClientIDMode="Static" runat="server"></asp:TextBox>
</p>
<p>
    <asp:TextBox ID="DisabledByAttributeTextBox" ClientIDMode="Static" runat="server"></asp:TextBox>
</p>
<p>
    <asp:Button ID="SubmitButton" runat="server" OnClick="SubmitButton_Click" Text="Submit" /> 
    <asp:Button ID="ClearButton" runat="server" Text="Clear Fields" OnClick="ClearButton_Click" />
</p>
<p>
    <asp:Button ID="PopulateFieldsButton" runat="server" Text="Populate Fields (ServerSide)" OnClick="PopulateFieldsButton_Click" />
    <input type="button" value="Populate Fields (ClientSide)" onclick="Populate();" />
</p>
<asp:Literal ID="OutputDisplay" runat="server"></asp:Literal>

I also added a basic javascript function to the page to set the Text value of the 4 text boxes for comparing the difference in postback results when the textboxes are populated via server side code or client side code.

<script type="text/javascript">
    function Populate() {
        var readOnly = document.getElementById("ReadOnlyTextBox");
        var disabled = document.getElementById("DisabledTextBox");
        var readOnly2 = document.getElementById("ReadOnlyByAttributeTextBox");
        var disabled2 = document.getElementById("DisabledByAttributeTextBox");

        readOnly.value = "ReadOnly By Property";
        disabled.value = "Disabled By Property";
        readOnly2.value = "ReadOnly By Atribute";
        disabled2.value = "Disabled By Attribute";
    }
</script>

Here is the C# code for the ASP.NET page. In the Page_Load event the readonly and disabled attributes are set for the relevant two textboxes. When the form is submitted the values of the tesxtboxes are read and displayed in a Literal webcontrol. There is also a PopulateFieldsButton_Click event to populate the tesxtboxes from server side.

protected void Page_Load(object sender, EventArgs e)
{
    ReadOnlyByAttributeTextBox.Attributes.Add("readonly", "readonly");
    DisabledByAttributeTextBox.Attributes.Add("disabled", "disabled");

	// uncomment below to compare effect of populating TextBoxes in form load at server side
    //SetTextBoxes();
}
      
protected void SubmitButton_Click(object sender, EventArgs e)
{
    var output = new StringBuilder();
    output.Append("Posted Values<br/>");
    output.AppendFormat("ReadOnly By Property TextBox: {0}<br/>", ReadOnlyTextBox.Text);
    output.AppendFormat("Disabled By Property TextBox: {0}<br/>", DisabledTextBox.Text);
    output.AppendFormat("ReadOnly By Attribute TextBox: {0}<br/>", ReadOnlyByAttributeTextBox.Text);
    output.AppendFormat("Disabled By Attribute TextBox: {0}<br/>", DisabledByAttributeTextBox.Text);
    OutputDisplay.Text = output.ToString();
}

protected void PopulateFieldsButton_Click(object sender, EventArgs e)
{
    SetTextBoxes();
}

protected void ClearButton_Click(object sender, EventArgs e)
{
    DisabledTextBox.Text = String.Empty;
    ReadOnlyTextBox.Text = String.Empty;
    ReadOnlyByAttributeTextBox.Text = String.Empty;
    DisabledByAttributeTextBox.Text = String.Empty;
}

private void SetTextBoxes()
{
    ReadOnlyTextBox.Text = "ReadOnly By Property";
    DisabledTextBox.Text = "Disabled By Property";
    ReadOnlyByAttributeTextBox.Text = "ReadOnly By Attribute";
    DisabledByAttributeTextBox.Text = "Disabled By Attribute";
}

On to the tests.
Test 1 – Populate server side.

• Ensure the fields are empty by clicking the Clear Fields button
• Click the Populate Fields (ServerSide)
• Click the Submit Button

The results show the Text value was posted back to all except the textbox with the disabled attribute set by C# code.

ReadOnly By Property TextBox: ReadOnly By Property
Disabled By Property TextBox: Disabled By Property
ReadOnly By Attribute TextBox: ReadOnly By Attribute
Disabled By Attribute TextBox: 

Test 2 – Populate client side

• Ensure the fields are empty by clicking the Clear Fields button
• Click the Populate Fields (ClientSide)
• Click the Submit Button

The results show the Text value was posted back to the server only on the textbox with the readoly attribute set by C# code.

ReadOnly By Property TextBox: 
Disabled By Property TextBox: 
ReadOnly By Attribute TextBox: ReadOnly By Atribute
Disabled By Attribute TextBox: 

So, if you want the Text value of the textbox to be posted to the server and you do not want the user to modify the contents of the textbox use C# code to set the ReadOnly attribute.

We had a situtation recently where we needed to allow users to download a pdf file from our server but we did not want to show the URL in the browser window. Although there are many ways to do this we opted to use an aspx page to retrieve the file and present it to the user. Knowing we will probably use this method againe in the application we decided to make sure the page was reusable.

The code below is of a webform load event. There are two querystring parameters, obviously these parameters are relevant to our requirements and you may user different parameters. The t parameter is the token, which is passed to the backend server as an identifier e.g. eventid, certificateid or something similar. The r parameter is to identify which url should be called.

protected void Page_Load(object o, EventArgs e)
{
    var token = Request.QueryString["t"];
    var report = Request.QueryString["r"];
    var URL = string.Empty;

    switch (report.ToLower())
    {
        case "u1":
            URL = System.Configuration.ConfigurationManager.AppSettings["url1"];
            break;
        case "u2":
            URL = System.Configuration.ConfigurationManager.AppSettings["url2"];
            break;
    }

    var fullURL = string.Format("{0}{1}", URL, token);
    var client = new System.Net.WebClient();
    try
    {
        Byte[] buffer = client.DownloadData(fullURL);
        if (buffer != null)
        {
            Response.ContentType = "application/pdf";
            Response.AddHeader("content-length", buffer.Length.ToString());
            Response.BinaryWrite(buffer);
        }
    }
    catch (System.Net.WebException ex)
    {
        if (((System.Net.HttpWebResponse)ex.Response).StatusCode == System.Net.HttpStatusCode.NotFound)
        {
            Server.Transfer("/404.aspx", false);
        }
    }
}

For us this page was called pdf.aspx, possible URLs this page will be called with are;

http://www.somedomain.com/pdf.aspx?t=1234&r=u1
http://www.somedomain.com/pdf.aspx?t=RY6N-UX6M&r=u2

It is possible to leave the token parameter blank if an identifier is not needed.

http://www.somedomain.com/pdf.aspx?t=&r=u2

The URLs of the backend server are stored in the web.config appSetting section, possible examples are.

<appSettings>
    <add key="url1" value="http://somebackendserver/{0}" />
    <add key="url2" value="http://anotherserver.addomain.net/certificates.aspx?ref={0}" />
</appSettings>

I have replaced the actual appSettings used with url1 and url2, your appSettings will have meaningful names.
The pdf file is downloaded to a byte array and presented to the user. If a WebException occurs the status of the response is checked and if a HttpStatusCode.NotFound status was returned from the backend server the applications 404 page is displayed.

There are a number of ways to extend this code and functionality relevant to any purpose.