...
When we develop an ASP site upgrade solution, we typically follow this process:
See also
Use the wizard to scan and load the sourcethe site directory and complete the preparation steps. This will create your gmStudio project, qualify files as includes or pages, and prepare the COM descriptions, the setup the initial translation script templates, and author the COM interface descriptions. I You do not want to run any translations or reports from the wizard as this is time consuming and premature at this stage.
At this point, I am you are done running the wizard and I you will switch to working in the gmStudio IDE.
Filter the files to just the PAGES as those with BuildType=PAGE. Build Type was identified by the Include Order process then . Next validate all of the PAGES to identify any the ones with missing dependencies. Resolve missing dependencies or remove defective pages. Do You do not attempt need to translate work with include files: they will be analysed and translated as needed for pages that reference them.
Next, attempt a single-page translation for each page, one at a time, and examine the log to see if there are any translation errors or warnings. If so investigate and resolve.
Examine the results of each page translation looking for late bound code, and if so, try to resolve to a stronger type by adding type hints (registy-fixtype) or other rule-based techniques. You may use the Target code search to examine and tabulate search results.
Deploy each page into translation as a single-base page web application project and attempt to build it. Each web application project will include the translated page as a webpage class and all of its direct and indirect includes translated to code classes. You will need to edit the User Command Batch script to facilitate the directory setup, cleanup, and deployment for each test build.
Examine and resolve the .NET build issues using various rule-based techniques such as fixtypes and EditFile commands in a GlobalSettings file as appropriate.
Generally speaking once all of the pages translate and build individually, the combined site script also builds. Once all of the page translations produce code a .NET project that builds, take those rules and integrate them with the SITE script that contains commands to compile all of the pages as a an integrated set.
Generally speaking once all of the pages translate and build individually, the combined site script also builds.
At this point, you will have a full ASP\.NET project for all of your pages that builds in Visual Studio.
Now I will At this point, you can may being to add the custom upgrades such as COM replacements, removing to do things like replace COM APIs , remove dead code, integrating integrate hand written code, integrating integrate runtime support assemblies as needed, apply custom project and web.config conventions, etc.
At some pointOnce this is done, you will have a an ASP\.NET solution that runs and has a structure worthy of debugging. You may then cut-over to finishing it manually, or you may continue improving the translation rules to correct defects in a systematic way.
At some point, the code will have no know known defects and you can work on packaging and publishing the site to a more production-like environment.
Once the ASP\.NET site works well enough in the production-like environment, you can go live.
See
...
Also
...