About the author

Vijay Kodali
E-mail me Send mail

Recent comments



The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2024

Read-only Textbox View state problem in ASP.NET

For a Textbox with Read-only property set to true, text is not be posted back to the server side.

From MSDN..

The Text value of a TextBox control with the ReadOnly property set to true is sent to the server when a postback occurs, but the server does no processing for a read-only text box. This prevents a malicious user from changing a Text value that is read-only.

To set a Textbox read-only and keep the text on post back, use the following code..

We can get it from the Request object as shown below…

  TextBox1.Text = Request[TextBox1.UniqueID]; //Another approach… 
  TextBox1.Text = Request.Form[TextBox1.ClientID.Replace("_", "$")];

Posted by vijay on Tuesday, July 31, 2007 2:20 PM
Permalink | Comments (2) | Post RSSRSS comment feed

Web Development Helper

It is a great tool for writing and debugging ASP.NET applications. It helps with following points.

  1. Tracing
  2. ViewState
  3. Caching (ASP.NET and HTTP)
  4. JavaScript
  5. DOM


Posted by vijay on Wednesday, July 18, 2007 1:41 PM
Permalink | Comments (1) | Post RSSRSS comment feed

LINQ Project overview

LINQ Project Overview by Don Box and Anders Hejlsberg

After two decades, the industry has reached a stable point in the evolution of object oriented programming technologies. Programmers now take for granted features like classes, objects, and methods. In looking at the current and next generation of technologies, it has become apparent that the next big challenge in programming technology is to reduce the complexity of accessing and integrating information that is not natively defined using OO technology. The two most common sources of non-OO information are relational databases and XML.

Rather than add relational or XML-specific features to our programming languages and runtime, with the LINQ project we have taken a more general approach and are adding general purpose query facilities to the .NET Framework that apply to all sources of information, not just relational or XML data. This facility is called .NET Language Integrated Query (LINQ).

We use the term language integrated query to indicate that query is an integrated feature of the developer’s primary programming languages (e.g., C#, Visual Basic). Language integrated query allows query expressions to benefit from the rich metadata, compile-time syntax checking, static typing and IntelliSense that was previously available only to imperative code. Language integrated query also allows a single general purpose declarative query facility to be applied to all in-memory information, not just information from external sources.

Categories: .Net 3.5 | LINQ
Posted by vijay on Monday, July 9, 2007 10:29 AM
Permalink | Comments (0) | Post RSSRSS comment feed