.NET Core Support Now Part of Key AWS Coding Services -- Visual Studio Magazine

.NET Core Support Now Part of Key AWS Coding Services

Developers working in the Amazon Web Services realm who have requested .NET Core support in some of the AWS coding tools got their wishes granted.

By David Ramel
07/13/2017

Cloud giant Amazon upgraded two services used for developing, building and deploying AWS applications so that those tools now support .NET. In particular, developers had inquired about the AWS tools CodeStar and CodeBuild having support for .NET Core, a lightweight, open source, modular platform used to create Web applications and services for Windows, Linux and Mac OSes.

CodeStar, introduced in April, is designed to integrate with existing IDEs and abstract some of the steps needed to build a toolchain for continuous integration/continuous deployment (CI/CD) on the AWS cloud. It comes pre-configured with a project management dashboard, an automated CD pipeline, and a Git code repository using AWS CodeCommit, AWS CodeBuild, AWS CodePipeline and AWS CodeDeploy. It also provides out-of-the-box integration with Atlassian's JIRA Software, which adds project management and issue tracking.

New .NET Core templates have been added to CodeStar, joining the initial templates available for developing Amazon EC2, AWS Elastic Beanstalk and AWS Lambda projects with the JavaScript, Java, Python, Ruby and PHP programming languages.

"Each template provisions the underlying AWS Code Services and configures an end-end continuous delivery pipeline for the targeted application using AWS CodeCommit, AWS CodeBuild, AWS CodePipeline, and AWS CodeDeploy," AWS' Tara Walker said in a blog post.

CodeBuild provides a fully managed project build service for compiling source code, testing the code and producing ready-to-deploy software packages, freeing developers from worrying about provisioning, managing and scaling their own build servers. The update now lets developers build and deploy .NET Core applications for Amazon EC2 and AWS Lambda.

"This new CodeBuild capability has enabled the addition of two new project templates in AWS CodeStar for .NET Core applications," Walker said.

"These new project templates enable you to deploy .NET Code applications to Amazon EC2 Linux Instances, and provides everything you need to get started quickly, including .NET Core sample code and a full software development toolchain," continued Walker, who added that many developers had inquired about .NET app development support.

In her post, Walker demonstrated how to use the new capabilities, noting that Visual Studio 2017 is required to leverage the new functionality, along with the AWS Toolkit for Visual Studio 2017.

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.