Amazon Web Services (AWS) has made it easier to deploy .NET applications to its cloud platform via its Visual Studio toolkit or the .NET CLI (command-line interface).

From within the Visual Studio IDE, the smoother deployment process comes with a new "Publish to AWS" wizard in the AWS Toolkit for Visual Studio 2022 in the Visual Studio Marketplace, which has been installed more than 45,000 times.

It's described as "an extension for Microsoft Visual Studio on Windows that makes it easier for developers to develop, debug and deploy .NET applications using Amazon Web Services."

The kit's description further reads: "The AWS Toolkit provides Visual Studio project templates that you can use as starting points for AWS console and web applications. As your application runs, you can use the AWS Explorer to view the AWS resources used by the application. For example, if your application creates buckets in Amazon S3, you can use AWS Explorer to view those buckets and their contents. If you need to provision AWS resources for your application, you can create them manually using the AWS Explorer or use the CloudFormation templates included with the AWS Toolkit to provision web application environments hosted on Amazon EC2."

For working with the .NET CLI, the functionality comes with the AWS Deploy Tool for .NET NuGet package.

"With sensible defaults for all deployment settings, you can now get your .NET application up and running in just one click, or with a few easy steps -- without needing deep expertise in AWS," Amazon said in a July 6 blog post. "You will receive recommendations on the optimal compute for your application, giving you more confidence in your initial deployments."

Indeed, those compute recommendations top the list of key capabilities as presented by AWS:

Several types of applications can be deployed (though not .NET Lambda functions), including:

As far as deployment targets, at this stage the new experience can work with Amazon Elastic Container Service (Amazon ECS) using AWS Fargate compute engine, AWS App Runner and AWS Elastic Beanstalk. Also supported is hosting Blazor WebAssembly applications in Amazon S3 using Amazon CloudFront as a content delivery network (CDN).

"The new deployment experience focuses on the type of application you want to deploy instead of individual AWS services by providing intelligent compute recommendations," AWS said in a separate July 6 post.

"One of the major new features is deployment projects. This new concept lets you customize deployments inside Visual Studio or the CLI, including the UI, and share it with the rest of your team members. Deployment projects allow teams to come up with custom deployment scenarios and still provide their team with interactive or scriptable deployments."

Meanwhile, the old deployment experiences -- "Publish to AWS Elastic Beanstalk" and "Publish Container to AWS" -- are still available in the the toolkit, though they're marked as Legacy in the context menu. AWS won't extend those wizards in the future and thus recommends that toolkit users migrate to the new "Publish to AWS" wizard. Developers are invited to open an issue on GitHub" for feedback, such as reporting missing features that are blocking migrations.

More information can be found in "Working with Publish to AWS in Visual Studio" documentation.

David Ramel is an editor and writer for Converge360.

Amazon Web Services (AWS) has made it easier to deploy .NET applications to its cloud platform via its Visual Studio toolkit or the .NET CLI (command-line interface).

In the regular monthly update to Python tooling for Visual Studio Code, Microsoft announced an improved setup experience for Jupyter notebooks, along with new inlay type hints for the Pylance language server.

This week, along with announcing the regular monthly update to Visual Studio Code (now at v1.69), Microsoft added a surprise: a private preview of VS Code Server, serving up the backend functionality that allows the editor to be run remotely or in a browser.

My Copilot does a lot of cool things, but sometimes it repeats itself and doesn't seem to want to compute the value of pi.

A new "getting started" experience for Java on Azure dev tooling promises to have IntelliJ jockeys up and running with their first deployment within a few minutes.

Problems? Questions? Feedback? E-mail us.