Transforming your .NET code - AWS Transform

Transforming your .NET code

After the AWS account administrator finishes Reviewing your plan to prepare for transformation, you can view the transformation progress on the Dashboard tab of your transformation job.

Note

In addition to transforming repositories and dependencies, AWS Transform can execute fully transformed (zero build errors) unit test projects. AWS Transform doesn't have access to unit test results prior to the transformation and can only share post-transformation results. You can then compare your baseline data, prior to transformation, with the post-transformation results to understand any potential gaps.

In the top right corner, you can see the job status, which has one of the following values:

  • Awaiting user input

  • Time elapsed

  • Running

You can also see the following icons:

  • A stop transformation icon

  • A refresh icon

  • A settings icon

The Dashboard provides a high level summary of the transformation. It shows metrics for the number of jobs transformed and transformation applied, and the estimated time to complete the transformation.

The Dashboard includes:

  1. The transformation Job details section, which lists the default settings and details of the transformation job, including:

    1. Target branch destination To transform your code, AWS Transform creates a new branch for the transformed code in your code repo.

    2. Target .NET version, which is .NET 8.0

    3. The AWS Transform job ID.

    4. The job settings:

      1. Exclude .NET standard projects

      2. Transform MVC Razor Views to ASP.NET Core Razor Views

  2. The Transformation summary section contains:

    1. The number of repositories selected for transformation

    2. The number of projects to be transformed

    3. The total lines of codes in these repositories and projects

After the transformation starts, pie charts appear in the Repository status, Package status, and Unit test status sections displaying progress in real time. The Unit test status shows the status of unit tests located in your repositories that AWS Transforms runs after transformation to test the transformed code. AWS Transform shares the executed test results, along with individual test name for customers to review the list of unit tests passed and failed.

Note

The Repositories section lists the repositories that AWS Transform recommends or that you selected for transformation. Select Download JSON to download a list of repositories, dependencies, and packages in your transformation plan.

Review the transformation summary report

After a transformation finishes for a repository, or when the transformation job completes, you can download a transformation summary report.

Download the transformation summary report from the Dashboard tab. Select Download, and choose Download as HTML or Download as JSON. This report provides an overview of the transformation, and information specific to each repository that was transformed, including:

  • Job Details

    • Transformation job overview

    • Transformation results overview

    • Files overview

  • Repositories list, and for each repository:

    • repository_name overview

    • Solution Transformation Summary

    • Project Details, including Status, Type, .NET Version, Total Lines of Code, Transformed Lines of Code, and Files Changed

Chat with AWS Transform about the transformation report

You can chat with AWS Transform about the transformation report after a repository has been completely processed or after the transformation job is completed. The Worklog tab displays this message for each repository that is available for chat: Repository repository_name transformation details are now available in chat for queries. It displays this message when the transformation job is completed: AWS Transform transformation job is completed.

To open the chat click the purple hexagonal icon in the lower right corner of the web console.

Here are some example prompts:

  • Which projects were successfully transformed?

  • Which projects were partially ported?

  • What changes were made to the repo_name repository?

  • What packages were upgraded in the project_name project?