.NET 6 was released two and a half months ago (2021-11-08). When it will be supported natively ?

[petarrepac]

And it was GA in Azure the same day.
Also, there were multiple betas and release candidates last year for .NET 6.

We are still waiting ...
I regularly have to downgrade some code from .NET 6 (C# 10) to .NETCore 3.1 to be able to use it in Lambda today.
:(

Can we at least get some guidance/roadmap when will .NET 6 be natively supported
(and not using container image or custom runtime) ?

Thanks.

[ashishdhingra]

Hi @petarrepac,

Good morning.

The support for .NET 6 with Lambda should be coming in the near future. While there is no exact timeline, for now, you may use .NET 6 with Lambda using the following approaches:

• Managed base container image - Pull from the ECR Public Gallery or use .NET 6 container image Blueprint in the AWS Toolkit for Visual Studio.
• Custom container image - Build a container image with the .NET 6 application packaged inside it. This PowerShell script will build a .NET 6 base container image.
• Custom runtime - The custom runtime bundles all necessary .NET 6 libraries in the zip file archive that is deployed to Lambda, see this example. For an ARM64 see this example.

Thanks,
Ashish

[petarrepac]

Hi Ashish, good evening. Thanks, I know about all this ways and they are great. But our current solution is based on Lambda native runtime and the management doesn't want to experiment with other ways. We will wait a bit more, but after that the investigation of other cloud platforms could happen. Thanks, Petar

…

On Mon, Jan 24, 2022, 19:48 Ashish Dhingra ***@***.***> wrote: Hi @petarrepac <https://github.com/petarrepac>, Good morning. The support for .NET 6 with Lambda should be coming in the near future. While there is no exact timeline, for now, you may use .NET 6 with Lambda using the following approaches: - Managed base container image <https://docs.aws.amazon.com/lambda/latest/dg/csharp-image.html> - Pull from the ECR Public Gallery <https://gallery.ecr.aws/lambda/dotnet> or use .NET 6 container image Blueprint in the AWS Toolkit for Visual Studio. - Custom container image - Build a container image with the .NET 6 application packaged inside it. This PowerShell script <https://github.com/aws/aws-lambda-dotnet/tree/master/LambdaRuntimeDockerfiles> will build a .NET 6 base container image. - Custom runtime - The custom runtime bundles all necessary .NET 6 libraries in the zip file archive that is deployed to Lambda, see this example <https://github.com/normj/LambdaNETCoreSamples/tree/master/CustomRuntimeListBucketsNET6>. For an ARM64 see this example <https://github.com/normj/LambdaNETCoreSamples/tree/master/ArmLambdaFunction#net-5-and-6-with-custom-runtimes> . Thanks, Ashish — Reply to this email directly, view it on GitHub <#1062 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFVBKRXZHTGQP6GKWXH2DDUXWNHPANCNFSM5MV46PXQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[normj]

Hi @petarrepac

I get the frustration and wish we had the support out already. For the most part we are code complete with .NET 6 and a lot of the client tooling has already been released. Due to the nature of coordinating the work and deployments across all the teams required for a managed runtime I'm sorry but a date is too fluid to give. Trust me we tried really hard to have the support out before the end of 2021 but due to emergent issues operational deployments took precedent over feature deployments. I appreciate every bodies patience and look forward to giving the good news of the release as soon as possible.

Norm

[petarrepac]

Hi @normj

Thank you for your answer and looking forward for good news.

Sometimes if the community doesn't push a little bit someone could get the impression there is small interest in the new capability/feature.

Thanks for all the hard work.

Kind regards,
Petar

[hounddog22030]

@normj Thanks for the update. Have you thought about releasing a "preview" edition?

[wjax]

Hi,

I am just leaving this comment to show my interest. My company is using mainly .net lambdas.
While I know that companies have different priorities at different times, I really think this one is key for the #dotnet community.

It is even more important as we are unable to use previous (.net 5) version as it was not LTS. So if we need native .net support in lambda, we have to go back to a version (3.1) that dates from december 2019

Regards

[egenita]

Hello,

I am also waiting here, our application can't go live yet since we are waiting for Net 6.
We can't afford to rollback it to v3.1.

We hope that at least we will know the estimated release date for Net 6 support.

Thank you!

[martincostello]

👀

[wjax]

Oh yeah!

Thanks a lot!

[normj]

@martincostello wins the prize of noticing first. Yes it is official .NET 6 support is out it took sometime to get all of the pieces released. Here is the blog post for the release.

https://aws.amazon.com/blogs/compute/introducing-the-net-6-runtime-for-aws-lambda/

[hounddog22030]

@normj -The section of the blog posted titled "Executable assemblies" is a little unclear to me. The way I understand this new approach means that the entry point into the Assembly is the same for multiple functions? Specifically, how would you handle multiple function handlers located in the same assembly? Am I completely misunderstanding the example? Thanks

[techthoughts2]

@normj - just wanted to say thanks for including this portion in your blog post:

If it exists, open the serverless.template file. For any AWS::Lambda::Function or AWS::Servereless::Function resource, set the Runtime property to dotnet6.

The CFN docs haven't been updated and I had (incorrectly) assumed it would have been dotnetcore6.0 ❌
Updating CFN references to Runtime: dotnet6 worked without issue!

[normj]

Closing now that the runtime is release. Thanks everybody for your patience.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[petarrepac]

Closing now that the runtime is release. Thanks everybody for your patience.

Thank you !!