 |
I began my profession as a .NET developer and have seen .NET evolve over the past couple of a long time. Like a lot of you, I additionally developed a number of enterprise functions in .NET Framework that ran solely on Home windows. I fondly keep in mind constructing my first enterprise utility with .NET Framework. Though it served us effectively, the expertise panorama has considerably shifted. Now that there’s an open supply and cross-platform model of .NET that may run on Linux, these legacy enterprise functions constructed on .NET Framework should be ported and modernized.
The advantages of porting to Linux are compelling: functions value 40 % much less to function as a result of they save on Home windows licensing prices, run 1.5–2 instances quicker with improved efficiency, and deal with rising workloads with 50 % higher scalability. Having helped port a number of functions, I can say the hassle is definitely worth the rewards.
Nevertheless, porting .NET Framework functions to cross-platform .NET is a labor-intensive and error-prone course of. It’s a must to carry out a number of steps, equivalent to analyzing the codebase, detecting incompatibilities, implementing fixes whereas porting the code, after which validating the modifications. For enterprises, the problem turns into much more advanced as a result of they could have lots of of .NET Framework functions of their portfolio.
At re:Invent 2024, we previewed this functionality as Amazon Q Developer transformation capabilities for .NET to assist port your .NET functions at scale. The expertise is on the market as a unified internet expertise for at-scale transformation and inside your built-in improvement surroundings (IDE) for particular person mission and resolution porting.
Now that we’ve included your precious suggestions and solutions, we’re excited to announce at present the final availability of AWS Rework for .NET. We’ve additionally added new capabilities to help tasks with non-public NuGet packages, port model-view-controller (MVC) Razor views to ASP .NET Core Razor views, and execute the ported unit checks.
I’ll increase on the important thing new capabilities in a second, however let’s first take a fast have a look at the 2 porting experiences of AWS Rework for .NET.
Massive-scale porting expertise for .NET functions
Enterprise digital transformation is usually pushed by central groups chargeable for modernizing lots of of functions throughout a number of enterprise models. Totally different groups have possession of various functions and their respective repositories. Success requires shut coordination between these groups and the applying homeowners and builders throughout enterprise models. To speed up this modernization at scale, AWS Rework for .NET offers an internet expertise that permits groups to attach on to supply code repositories and effectively rework a number of functions throughout the group. For choose functions requiring devoted developer consideration, the identical agent capabilities can be found to builders as an extension for Visible Studio IDE.
Let’s begin by taking a look at how the online expertise of AWS Rework for .NET helps port lots of of .NET functions at scale.
Internet expertise of AWS Rework for .NET
To get began with the online expertise of AWS Rework, I onboard utilizing the steps outlined within the documentation, sign up utilizing my credentials, and create a job for .NET modernization.
AWS Rework for .NET creates a job plan, which is a sequence of steps that the agent will execute to evaluate, uncover, analyze, and rework functions at scale. It then waits for me to arrange a connector to connect with my supply code repositories.
After the connector is in place, AWS Rework begins discovering repositories in my account. It conducts an evaluation targeted on three key areas: repository dependencies, required non-public packages and third-party libraries, and supported mission varieties inside your repositories.
Primarily based on this evaluation, it generates a beneficial transformation plan. The plan orders repositories in keeping with their final modification dates, dependency relationships, non-public package deal necessities, and the presence of supported mission varieties.
AWS Rework for .NET then prepares for the transformation course of by requesting particular inputs, such because the goal department vacation spot, goal .NET model, and the repositories to be reworked.
To pick out the repositories to rework, I’ve two choices: use the beneficial plan or customise the transformation plan by choosing repositories manually. For choosing repositories manually, I can use the UI or obtain the repository mapping and add the personalized listing.
AWS Rework for .NET mechanically ports the applying code, builds the ported code, executes unit checks, and commits the ported code to a brand new department in my repository. It offers a complete transformation abstract, together with modified recordsdata, check outcomes, and steered fixes for any remaining work.
Whereas the online expertise helps speed up large-scale porting, some functions might require developer consideration. For these circumstances, the identical agent capabilities can be found within the Visible Studio IDE.
Visible Studio IDE expertise of AWS Rework for .NET
Now, let’s discover how AWS Rework for .NET works inside Visible Studio.
To get began, I set up the newest model of AWS Toolkit extension for Visible Studio and arrange the stipulations.
I open a .NET Framework resolution, and within the Answer Explorer, I see the context menu merchandise Port mission with AWS Rework for a person mission.
I present the required inputs, such because the goal .NET model and the approval for the brokers to autonomously rework code, execute unit checks, generate a change abstract, and validate Linux-readiness.
I can assessment the code modifications made by the brokers domestically and proceed updating my codebase.
Let’s now discover among the key new capabilities added to AWS Rework for .NET.
Assist for tasks with non-public NuGet package deal dependencies
Throughout preview, solely tasks with public NuGet package deal dependencies had been supported. With normal availability, we now help tasks with non-public NuGet package deal dependencies. This has been probably the most requested options through the preview.
The function I actually love is that AWS Rework can detect cross-repository dependencies. If it finds the supply code of my non-public NuGet package deal, it mechanically transforms that as effectively. Nevertheless, if it will probably’t find the supply code, within the internet expertise, it offers me the flexibleness to add the required NuGet packages.
AWS Rework shows the lacking package deal dependencies that should be resolved. There are two methods to do that: I can both use the offered PowerShell script to create and add packages, or I can construct the applying domestically and add the NuGet packages from the packages folder within the resolution listing.
After I add the lacking NuGet packages, AWS Rework is ready to resolve the dependencies. It’s finest to supply each the .NET Framework and cross platform .NET variations of the NuGet packages. If the cross platform .NET model will not be accessible, then at a minimal the .NET Framework model is required for AWS Rework so as to add it as an meeting reference and proceed for transformation.
Unit check execution
Throughout preview, we supported porting unit checks from .NET Framework to cross-platform .NET. With normal availability, we’ve additionally added help for executing unit checks after the transformation is full.
After the transformation is full and the unit checks are executed, I can see the leads to the dashboard and consider the standing of the checks at every particular person check mission degree.
Transformation visibility and abstract
After the transformation is full, I can obtain an in depth report in JSON format that provides me an inventory of reworked repositories, particulars about every repository, and the standing of the transformation actions carried out for every mission inside a repository. I can view the pure language transformation abstract on the mission degree to grasp AWS Rework output with project-level granularity. The abstract offers me with an outline of updates together with key technical modifications to the codebase.
Different new options
Let’s have a fast have a look at different new options we’ve added with normal availability:
- Assist for porting UI layer – Throughout preview, you possibly can solely port the enterprise logic layers of MVC functions utilizing AWS Rework, and also you needed to port the UI layer manually. With normal availability, now you can use AWS Rework to port MVC Razor views to ASP.NET Core Razor views.
- Expanded connector help – Throughout preview, you possibly can join solely to GitHub repositories. Now with normal availability, you may hook up with GitHub, GitLab, and Bitbucket repositories.
- Cross repository dependency – When you choose a repository for transformation, dependent repositories are mechanically chosen for transformation.
- Obtain evaluation report – You’ll be able to obtain an in depth evaluation report of the recognized repositories in your account and personal NuGet packages referenced in these repositories.
- E mail notifications with deep hyperlinks – You’ll obtain electronic mail notifications when a job’s standing modifications to accomplished or stopped. These notifications embody deep hyperlinks to the reworked code branches for assessment and continued transformation in your IDE.
Issues to know
Some further issues to know are:
- Areas – AWS Rework for .NET is mostly accessible at present within the Europe (Frankfurt) and US East (N. Virginia) Areas.
- Pricing – At present, there may be no further cost for AWS Rework. Any sources you create or proceed to make use of in your AWS account utilizing the output of AWS Rework might be billed in keeping with their normal pricing. For limits and quotas, discuss with the documentation.
- .NET variations supported – AWS Rework for .NET helps reworking functions written utilizing .NET Framework variations 3.5+, .NET Core 3.1, and .NET 5+, and the cross-platform .NET model, .NET 8.
- Software varieties supported – AWS Rework for .NET helps porting C# code tasks of the next varieties: console utility, class library, unit checks, WebAPI, Home windows Communication Basis (WCF) service, MVC, and single-page utility (SPA).
- Getting began – To get began, go to AWS Rework for .NET Person Information.
- Webinar – Be a part of the webinar Speed up .NET Modernization with Agentic AI to expertise AWS Rework for .NET by a dwell demonstration.
– Prasad
How is the Information Weblog doing? Take this 1 minute survey!
(This survey is hosted by an exterior firm. AWS handles your info as described within the AWS Privateness Discover. AWS will personal the information gathered through this survey and won’t share the knowledge collected with survey respondents.)
