ASP.NET Core 2 Support

[uxsoft]

With ASP.NET Core 2 there is a new way to create a webhost

Instead of:
protected override void Init(IWebHostBuilder builder)
...

We now have:
public static IWebHost BuildWebHost(string[] args) =>
WebHost.CreateDefaultBuilder(args)
.UseStartup()
.Build();

[normj]

When Lambda supports .NET Core 2.0 we'll take a look at updating the Amazon.Lambda.AspNetCoreServer for the changes to ASP.NET Core 2.0.

[beeradmoore]

@normj out of curiosity, now that beanstalk supports .NET Core 2.0 will that be coming to Lambda anytime soon, or not so because we need .NET Core 2.0 to be lts?

[arpit-nagar]

Any updates by when we can have support of .Net Core 2.0 ?

[beeradmoore]

@arpit-nagar, .NET Core 2.0 is not LTS (Long Term Support) so as far as they have said elsewhere it won't suddenly get added.

As to my previous comment wiht beanstalk getting .NET Core 2.0 so can we have it now, normj has a response over here regarding that.

I feel this should now be closed.

[FrederikNygaardSvendsen]

I really need to know if support for .net core 2.0 is in development, and if not, if support is even planned... This is a huge deal

[beeradmoore]

@FrederikNygaardSvendsen , aws-lambda only supports LTS versions of dotnetcore, so you need to go ask the dotnetcore people when 2.0 is going to become LTS, nothing is happening here until then.

[normj]

@FrederikNygaardSvendsen I can't give any timing or details but I will say we know the a new .NET Core Lambda runtime is critical to the community and we are working hard on the next version.

[FrederikNygaardSvendsen]

@normj Thanks for letting me know

[Kralizek]

@normj maybe you should add this news in the ReadMe considering how many requests you are getting :P

[normj]

Closing this in favor of tracking the upcoming .NET Core 2.0 support with issue #149