...
- Create a Web Application Project File for the entire site or a subset of pages. This project will reference all translated files and allow you to pre-build and thus help you validate the .NET logic. A web application project also facilitates debugging and deployment. It is also possible to produce a Web Directory project with some minor configuration changes.
- Rewrite all server-side VBScript to C# or VB.NET (Note: gmStudio does not support translating server-side JScript to .NET)
- gmStudio has a special feature that can translate client-side VBScript to client-side JavaScript. (contact us for details)
- Migrate ASP page directives to ASP.NET page directives
- Infer stronger types everywhere
- Deal with different semantics of ASP intrinsic collections (e.g., Response, Request)
- Replace external COM components with .NET components
- Restructure pages to ASPX pages with CodeBehind files
- Consolidate all declarative script code into CodeBehind files
- Convert #Includes to Code classes. An Author_Markup function is implemented in each include-class to render any markup that was originally contained in the #include file. Note that it is possible to migrate a specified #include file to a Web User Control using an appropriate registry-fixstatus command.
- Add logic to each page/include to declare and initialize any referenced code classes from includes.
- Rewrite markup formerly in render functions to use Response.Write calls
- Standardize and clean up HTML markup
...