Most browsers support cookies of up to 4096 bytes. Because of this small limit, cookies are best used to store small amounts of data, or better yet, an identifier such as a user ID. The user ID can then be used to identify the user and read user information from a database or other data store.
Browsers also impose limitations on how many cookies your site can store on the user's computer. Most browsers allow only 20 cookies per site; if you try to store more, the oldest cookies are discarded. Some browsers also put an absolute limit, usually 300, on the number of cookies they will accept from all sites combined.
A cookie limitation that you might encounter is that users can set their browser to refuse cookies. If you define a P3P privacy policy and place it in the root of your Web site, more browsers will accept cookies from your site. However, you might have to avoid cookies altogether and use a different mechanism to store user-specific information.
Although cookies can be very useful in your application, the application should not depend on being able to store cookies. Do not use cookies to support critical features. If your application must rely on cookies, you can test to see whether the browser will accept cookies. There are code snippets you can do to check if your client browser has cookies enabled or not. I will explain later about this throughout the article.

We will create a custom dropdown conrol using a datasource. This code provides us to fill a dropdrown list using a datasource. This code also displays us ASP.NET is easier than classical ASP to generate custom controls.

ASP.NET 2.0 Training : Data Bound Controls - In this tutorial you will learn about Data Bound Controls - The Hierarchy of Data Bound Controls, Simple Data Bound Controls, Composite DataBound Controls and Hierarchical Data Bound Controls.

In this article we will take a quick look at two methods for creating SHA1 passwords for use on the web.

In brief we show how to generate SHA1 hashes that are Forms Authentication compatible via

Developing websites to support multiple languages can be a challenging and time-consuming process. With standard HTML pages this involves creating and maintaining duplicate versions of each page for each supported language as well as having the language content embedded into the HTML, where content can?t easily be edited. While the process improved slightly with the introduction of scripting technologies such as ASP and PHP, no significant development or maintenance time was saved. For those of you who have to develop multi-lingual interfaces and applications, you?ll be glad to know that ASP.Net makes things considerably easier.

ASP.Net and the .Net framework ship with support for multilingual applications, namely in the form of Resource Files, the CultureInfo class and the System.Globalization and System.Resources.ResourceManager namespaces. Unfortunately in its present state, localizing content in ASP.Net applications is still a tedious process. Like everything else .Net though, the object model and sheer power available makes extending what's already available and developing new functionality to support better localization easy as 1 - 2 - 3.