Create an RSS feed using ASP.NET 2.0 - ASP.NET tutorial

Category: ASP.NET tutorials - Difficulty:

Iron Speed Designer generates database and reporting applications for .NET in minutes, straight from your database. Quickly create visually stunning, feature-rich Web 2.0 applications that are easy-to-customize and ready-to-deploy. If you need an app built today, use Iron Speed Designer! Simply point to an existing database and let the Iron Speed Designer wizards build a sophisticated, database-driven application that’s ready to deploy. In just minutes, Iron Speed Designer generates your application’s Web pages, user interface code and data access logic. Say ‘good bye’ to hand-coding ASPX pages and SQL statements. Iron Speed Designer eliminates routine infrastructure programming, freeing you to focus on your business logic. You can customize every aspect of your application, from its visual style to the underlying code. Applications have a straightforward class hierarchy that makes it easy to extend and preserve your code modifications. You enjoy unrestricted access to 100% of the code, and there are no run-time license fees or special server software requirements for applications built with Iron Speed Designer.

The author writes "With ASP.NET you can configure the 'ASP.NET engine' to automatically restart itself when certain criteria are met. For example, if the Web server has 100 requests queued up, you may wish to have the Web server restarted, assuming that some script or DLL is hanging the Web server. Additionally, you can set requirements on restarting the Web server on the memory usage, the total number of requests, or by the total time the Web server's run. This proactive approach was implemented by the ASP.NET team in order to increase the overall uptime of a Web site running ASP.NET: if the memory suddenly shoots through the roof, the Web server can be restarted, reigning in the memory usage and starting anew. The information regarding the life cycle of the current (and past) ASP.NET processes can be examined through the use of the ProcessModelInfo class." This article examines how to retrieve and present such information.

System.Web.UI.Page manages a list of server-side controls, and it's the job of each server-side control to render a particular portion of the page. ASP.NET broadly classifies server-side controls into two categories:

Rendering controls (controls that completely manage the rendering process)

Composite controls (multiple server-side controls bundled into a single unit)

This tutorial focuses on the first type: custom rendered controls. We'll see how the control works once it's part of a Web page. Along the way we'll cover topics such as how controls manage events and how they detect the differences in client browsers.

In this article we will take a quick look at two methods for creating SHA1 passwords for use on the web using .NET. It is dangerous to store passwords anywhere in plain text!! SHA1 gives a quick and easy way to encode a password into a non-human readable form. This means it is safer to store in a database, and should the database be viewed by anyone who shouldn't know the passwords, it will be much more difficult for them to work out what a user's password is.

Sometimes you will need to export some data from an ASP page and use another charset than the encoding you have specified in Web.config. This short sample EncodeString function lets you write response string data using any code page.