| We have taken a brief look at the features of ASP.NET, most striking of which are the server controls, session management, and data access. Intrinsic controls allow us to continue using the existing controls while providing the capabilities of .NET. List controls provide data binding, which makes it easy to display data without too much use of ADO.NET. Validation controls take care of the validation routines without additional lines of code. In-process session handling in ASP.NET is different from that in ASP because of the basic difference in the manner in which ASP and ASP.NET pages are executed. Interoperability in .NET provides the ability to continue using existing COM components in the .NET environment. The configuration file web.config makes application configuration easy and readable. The concept of disconnected data access forms the basis of ADO.NET, which is vastly different from the existing ADO. We have also provided a brief overview of security concepts in .NET, application deployment, and multiple-language support in .NET with reference to ASP.NET. This chapter covered how ASP and ASP.NET pages are processed separately on a single Web server and as a result ASP and ASP.NET pages can coexist within the same Web application. This helps in migrating the application part by part, upgrading some parts of the application to ASP.NET while maintaining others in traditional ASP. The recommended migration approach is a four-step process. First, the developer has to choose an application to migrate and decide the strategy that best suits the requirements for migration. Next, certain code changes should be made to the existing ASP application so that the errors encountered during migration are reduced. Modifications in security settings are recommended only to ensure a smooth migration, but they are not mandatory. The modifications can be made either by changing the user group of the ASPNET account or by changing the <processmodel> section of the machine.config .  | 
