...
- Select [Open .NET Project Folder] on the migration unit context menu open the deployment folder for that unit.
- Select [View\Deploy Folder] to open the deploy folder for your migration project.
Default VB6 Deployment
Translating a VB6 migration unit produces a set of files that correspond to the ones referenced by the source VBP:
...
[WorkspaceRoot]\[MigName]\deploy\ where: [WorkspaceRoot] is the workspace root folder [MigName] is the migration project name
| Tip | ||
|---|---|---|
| ||
Not getting anything except empty project files from your web site translation? gmStudio probably failed the deployment step because of missing sub-directories in the \[wrokspace]\deploy folder. Look at the deploy log and you will probably see error messages to that effect. This is a common mistake with ASP migrations because by default setting up the ASPX site directory is a manual preparation step. What we normally do is create a full empty folder tree in the deployment root using a tool like robocopy. Of course web sites depend on many types of "pulp" files (images, css, etc.) that will also be needed to run and test the new site so you may want to copy those as well. Again robocopy is good for setting up the "test site" directory from your current site directory. |
Example Web Deployment
The DemoFMSWeb_csh.gmproj sample has the following settings:
...