When you deploy to ASP, the controller performs several additional procedures during the deployment process:
Changes the file extension to ASP for those files that contain server-side scripts. When the deployment controller changes a file's extension to ASP, it is possible that some links to that file might break.
To avoid breaking links, use the ASP extension for the target file within your Web target. If two different files have the same file names but different extensions (for example TEST.HTM and TEST.HTML), and both contain server-side code, the deployment controller will rename both files to the same name (for example, TEST.ASP) and overwrite one of the files. To prevent this, assign your files unique file names.
Creates a GLOBAL.ASA file. This file contains a Session_onStart routine that establishes session variables for each database connection used in the pages you deploy.
If your project already contains a GLOBAL.ASA file, the deployment controller updates it to include the necessary code instead of creating a new file.
To allow your Web pages to use the predefined connections, you need to create a data source for each connection if one does not already exist. The DSN name for each data source must match the DSN specified in the ConnectionString session variable.
When you deploy a Web page that uses the Web Target object model, the deployment controller automatically includes an object model file in the page. When you deploy to ASP, the controller for ASP generates a server-side include (<!--#INCLUDE -->) statement that specifies the name of the target in the path to the object model file, as shown in the following example:
<!--#INCLUDE VIRTUAL="/MyProject/ObjMod.js"-->
Any references to the Web Target object model do not work when you deploy to ASP unless the name of the virtual mapping you deploy to matches the name of the target exactly. So, the <!--#INCLUDE --> statement shown above would work only if the virtual mapping were MyProject.
After deploying the target to an ASP Web site, you may need to perform some additional procedures to get your Web application up and running. For detailed instructions, see the documentation provided for your Web and application servers.
