- This topic has 1 voice and 0 replies.
August 30, 2018 at 6:29 pm #100070557AbidParticipant
.Net Core and AWS Lambda
Do you know that Amazon Web Services Inc. (AWS) announced its Lambda service — for running programming code without having to provision or manage servers — now supports .NET Core 2.1
.NET Core is Microsoft’s newest take on the .NET Framework, which has been modularized, made cross platform and open sourced.
AWS Lambda supported .NET Core 2.0 early this year, and support for the runtime for other coding tools was announced last summer.
Now, AWS Lambda supports .NET Core 2.1, which will be Microsoft’s Long Term Support (LTS) offering going forward. However, there was a flaw discovered in .NET Core 2.1 that will extend the life of .NET Core 2.0.
“Microsoft will end its support for .NET Core 2.0 at the beginning of October, 2018,” AWS said in a post yesterday (July 9). “At that time, .NET Core 2.0 AWS Lambda functions will be subject to deprecation per the AWS Lambda Runtime Support Policy. After three months, you will no longer be able to create AWS Lambda functions using .NET Core 2.0, although you will be able to update existing functions. After six months, update functionality will also be disabled.”
AWS said developers will now be able to take advantage of new features introduced in .NET Core 2.1, including a more performant HTTP client. “This is particularly important when integrating with other AWS services from your AWS Lambda function,” the post said. Other new features highlighted in the post include new Span<T> and Memory<T> language features.
More information is provided in another blog post. “The easiest way to get started is with the AWS Toolkit for Visual Studio which includes project templates for individual C# Lambda functions, full C# serverless applications, and tools to publish both project types to AWS,” it said.
The .NET Core 2.1 runtime is now available in all regions where Lambda is available.
- You must be logged in to reply to this topic.