gmStudio's approach to ASP translation process is directed by translating groups of pages (.asp files, aka. Web Sites). This involves process requires preparing a Site translation script containing a list of pages .asp/.asa files and processing that script. The list of files should contain only "pages", not include #include files. Include The #Include files are be automatically process translated when you process translate a page that references an #include . Processing #includes either directly or indirectly, through another #include.
Translating #includes directly does not make sense because they often depend on content contain code that depends on symbols declared in other #includes that may be are only available when integrated through the a page.
gmStudio can help you identify which files are pages and includes automatically which ones are #includes using the Set Build Order operation from the Tools menu. In simple terms: any .asp file found is in an #include element is considered to be an #include, otherwise it is considered a page. See Prepare Web Site Script for more details.
However, there can still be a problem: some pages may no longer be activenot be used by the production web site. They These pages are in the site directory, but they are never referenced browsed by a user or used in any other process operation such as a redirect. We call these dead pages and they often contain out of date or invalid code that causes can cause problems with translation. So, an important step in preparing for an ASP upgrade is identifying precisely which files are dead and which are active . The dead files should all be removed as the first step in preparing a copy of the site for translationand removing dead files from the site folder and the site script. This clean up work should be one of the first steps done when preparing your site for translation. Failing to do this cleanup will waste time during your upgrade project and increase technical debt and maintenance costs afterwards.
There are a lot of ways to deduce which if files are activeused or not:
- Exclude File files based on names (e.g. named "file-old.asp" or "copy of file.asp", etc.)
- Exclude Folders folders based on names (e.g. named "backup\" or "old\", etc.)
- Looking at Exclude files that are clearly not active or are defective in some way
- Include files that are reported as served in Production web logs to see pages actually served
- Analysis of navigation directed by code or data
- Redirect
- Include files in redirect statements in pages know known to be active• Hrefs active
- Include files in href tags in pages know known to be active
- System documentation (only upgrade the pages that you know how to use)
- Consider system documentation if available and up to date
- Consider Test Plans (only upgrade the pages that you know how to test)
- Page content (e.g. files that are clearly not active pages or are defective in some way)
Failing to do this cleanup will waste time during your upgrade project and increase technical debt and maintenance costs afterwardsContact Us if you would like help with planning as ASP upgrade using gmStudio.