Asp.net core 2.2 support in Lambda

[PaymonK]

It seems the latest version of .net supported in Lambda is 2.1.4. That is causing compatibility problems for us.

When will 2.1.5 or ideally 2.2 be supported?

[normj]

Lambda is currently running 2.1.5 which you can see from our version status table.

Out of curiosity what were the compatibility problems?

[PaymonK]

Apologies, I didn't notice that 2.1.5 was now supported. My data was a few days old.
We were experiencing problems running 2.1.4 in development mode in general. Nothing to do with Lambda actually.

[ZeinSleiman]

What about 2.2?The version table still mentions 1.17 as Microsoft latest release.

[vellozzi]

That means it's the latest patch of the corresponding minor version. E.g. 1.0.13 is the latest patch of 1.0.

We're only planning to support LTS versions of .NET Core. .Net Core 2.0 was an exception to that because at the time we believed it was going to be LTS.

We are talking about how we might help customers work with Lambda's custom runtime feature though. But we don't have an ETA for that work.

[michelmob]

Hi guys! I know this thread is closed but would like to hear from you guys if we already have another solution/workaround.

I have some lambda functions running using .net core 2.1 but I had to update my applications to .net core 2.2 and got in the hell with other packages.

I got the documentation to use custom runtime but I would like to understand what options I have. Can you guys help me ?

Thank you so much!

[normj]

@michelmob I suggest following this GitHub issue tracking our effort to open source our .NET Core Lambda runtime code. #405

[RoyiNamir]

@normj

Hi. I don't understand.

This article :
https://aws.amazon.com/blogs/developer/announcing-amazon-lambda-runtimesupport/

Says that 2.2 is supported.

This means you can now author Lambda functions using .NET Core 2.2 and .NET Core 3.0 preview.
Amazon.Lambda.RuntimeSupport is available as source code on GitHub, or as a NuGet package.

But on the other side there's this table :

I'm confused.

Can I write Lambda targeting dot net core 2.2 ? or Can't I ?

What am I missing ?

[clearwaterstream]

@RoyiNamir, out-of-box currently only 2.1 is supported, 2.2 is not.

You can deploy an app running on 2.2 using a custom runtime. Read high level intro here and see an example app here

I would like to note that apps using a custom runtime do take longer to deploy. It's not the extra files that make the deployment longer, I think it's the warm-up or initialization post deploy that's taking the extra time.

You could wait for AWS .NET team to release ASP.NET Core 2.2 support but by the time they do, 3.0 may be out and you will end up in the same boat again -- waiting. So may not be a bad idea to invest in setting up a CustomRuntime now.

Over the years, I've waited for AWS to release .NET 4.7.2 way back when they were running on 4.7 -- it took a while. Had to custom bootstrap our Elastic Beanstalk instances with 4.7.2. I've also waited for 2.1.

I think generally AWS takes a while before they refresh their .NET platform -- as they should. Before developing new apps, I check AWS Elastic Beanstalk Supported Platforms and AWS Lambda Runtimes so that there are no surprises when deploy comes around.

If you want to have more control over the platform, invest in setting up CustomPlatform now.

[petarrepac]

I think AWS announced they will support only LTS .NET Core releases. The only exception for now was .NET Core 2.0.

• 2.1 is LTS
• 2.2 in not LTS.
• 3.0 will be released in September 2019 and is not LTS
• 3.1 will be an LTS, coming in November 2019

more here: https://github.com/dotnet/core/blob/master/roadmap.md