You can migrate from ASP application to ASP.NET application in two ways: Horizontal migration and Vertical migration. In Horizontal application, one complete tier of code has to be replaced. In Vertical application, you have to modify every piece of application through all n-tiers. You can also migrate to ASP.NET application by just changing file extension. But this requires VBScript to be changed to VB.NET. In case, you do not want to integrate an ASP application to ASP.NET, you can run both application on same server. They both have completely different processing engines.

Thus, ASP to ASP.NET migration means complete object-oriented programming structure, easy maintenance, reusable code, automatic documentation from reverse engineering, ASP.NET controls, and multiple-language debugger.

To access online version of above article, go to http://www.dotnet-guide.com/migration.html

• Code generation: Used to covert ASP.NET pages into ASP.NET Classes and to generate source files in multiple languages. The System.CodeDOM is used to derive code generation ASP.NET Classes.

• IO: Used to work with files and all other stream types. It uses System.IO namespace.

• Reflection: Used to provide support for load assemblies, inspecting types within assemblies, and createing instances of types. It uses System.Reflection namespace.

• Security: Used extensively to build a security strategy for ASP.NET pages. It also provides some base services such as authentication, authorization, permission sets, policies, and cryptography. It uses System.Security namespace.

There are numerous ASP.NET Classes. If you want to find and locate a particular class then you can use WinCV tool. This file is located in C:programfilesMicrosoft.NetFrameworkSDKBin directory. You can open this file from Run command.

To access online version of above article, go to http://www.dotnet-guide.com/classes.html