Overview

All statements/constructs of the target code compile with no compiler errors. In addition, specialized project elements (e.g., Forms) are accessible through their specialized editors provided by the target development environment. Build Complete is an important milestone because it means you can begin to use contemporary .NET tools that work on compiled assemblies, not source code, and it also means that you can begin testing the application to identify and eliminate runtime defects.

It is our intention to produce Build-Complete codes in a completely automated manner right out of the box. We feel this is a reasonable baseline level of functionality for a migration tool: if the source code builds with VB6/ASP/COM, the target code should build in .NET.

Standard .NET Build Test

The .NET Build Test verifies that the translations can be processed by MSBuild:

Test Plan	Notes
Steps	Highlight the migration task you wish to validate and Select [Deploy Translation] the [Build Translation] from the Task Context Menu.
Expected Results	The NetBlds field is set to a "SUCCESS" This indicates that the build process was successful.
Error Condition 1	The NetBlds field is set to "ERROR" This indicates that the build process encountered errors while processing your .NET codes.
Error Condition 2	The NetBlds field is set to "SKIP" This indicates that the deployment process encountered errors while deploying your .NET codes. See Deployment Test above.
Troubleshooting	Display the Task Details tab and click the Build log button. Review the log to determine the nature of the error. You may check the [Grid] box to see the most relevant build log messages in a grid report. Double clicking a report record will take you to the source where the error was encountered.
Resolution	.NET build problems can occur for a variety of reasons ranging from missing externals, to crude syntax errors, to more advanced compile time validation. Use Visual studio to help you diagnose the issues. Once a build error is resolved you should implement the fix in the migration configuration so that it will not occur in the next translation cycle. See the discussion of the Translation Tuning cycle below.

An alternative means of identifying translation problems is to run the Build Logs report.

Browser not supported