.NET framework is a Windows Component that supports the building and running of windows applications and XML Web services. The purpose of the component is to provide the user with a consistent object oriented programming environment whether the code is stored locally or remotely. It aims to minimize software deployment and versioning conflicts and also promote safe execution of code including codes executed by trusted third parties. It is directed towards eliminating performance problems of scripted or interpreted environments. The effort is to make developer experience consistent across a variety of applications and platforms and create communication standards that help .NET framework applications integrate with all other web based applications.

This article presents a simple method for securing your ASP.NET web pages, requiring almost no code development. In this article, you'll be introduced to the components that .NET provides that significantly reduce the amount of code you have to write in order to secure your website pages. You'll learn about Forms Authentication, User Identity, XML configuration files, and authorization tickets. And you'll learn how to store username and password information in simple XML configuration files.

In this paper, we will look at the structure of a very simple ASP.NET page and how that page is rendered in the visitor's browser. Then we will look at the Page class, which is the .NET class that all your ASP.NET pages are based on. After that, we will review basic compiler directives that you can place on your page. At the end of the chapter, we will review a simple Quiz ASP.NET page that demonstrates the basics of an ASP.NET page.

Marcus Mac Innes demonstrates how security on a web site can be compromised by taking advantage of holes within the application code. These holes can be discovered by using a series of probes which disclose whether or not vulnerability exists. He also demonstrated using a Cross Site Scripting attack how the Forms Authentication cookie could be stolen and silently sent to an attacker's website to be stored for later use. The key message of the talk is to ensure that all user input is validated before any other processing is done. This together with strict use of secure coding standards would have disabled any attacker's opportunities. Source code included.

Create stored procedures with Output parameters and return values and use them in .NET

This paper looks at some of the specific benefits you can achieve in migrating applications from ASP, and presents five distrinct strategies for a migration, based on its perceived strategic value and your desired timeframe for results. A scorecard with key questions about your migration allows you to quickly arrive at an initial estimate of a migration's complexity. Finally, it outlines the major activities involved in the four phases of a migration project.

ASP.NET pages are dynamically compiled on demand when first required in the context of a Web application. Dynamic compilation is not specific to ASP.NET pages (.aspx files); it also occurs with Web Services (.asmx files), Web user controls (.ascx files), HTTP handlers (.ashx files), and ASP.NET application files such as the global.asax file. But what does it mean exactly that an ASP.NET page is compiled?

Web Services Enhancements for Microsoft .NET (WSE) provides an implementation of the Web services architecture for developers creating Web services by using ASP.NET and Microsoft .NET Framework client applications. It allows developers to incorporate security, routing, and attachment features in their application.

Learn the difference between Classic ASP techniques and the new Templating method in ASP.NET.

William Fawthrop (aka Informant) gives us his first .NET article in what promises to be a great new series of articles from him. The author specializes in .NET migration as well as creative solutions in the .NET framework. In this article: A C# 'Hello World' with a loop.