You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 18, 2022. It is now read-only.
I have been trying to follow your step by step guide for ‘setting up your AWS Lambda C# development environment’.
With regards to step 3...you have advised ‘do not install any version higher than .NET core 1.0. However the link you have provided only allows for download of .NET core 2.1.
When I attempt to publish my lambda function...I can select the Language runtime 1.0 but I cannot change the Framework to 1.0 to match the image you have provided.
When I proceed, I am met with the following error: The framework netcoreapp2.1 is a newer version than Lambda runtime dotnetcore1.0 supports.
Apologies If this seems like a very basic query, I am very new to programming and IT in general(6mths).
Any help you can provide would be greatly appreciated.
Steve
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
I have been trying to follow your step by step guide for ‘setting up your AWS Lambda C# development environment’.
With regards to step 3...you have advised ‘do not install any version higher than .NET core 1.0. However the link you have provided only allows for download of .NET core 2.1.
When I attempt to publish my lambda function...I can select the Language runtime 1.0 but I cannot change the Framework to 1.0 to match the image you have provided.
When I proceed, I am met with the following error: The framework netcoreapp2.1 is a newer version than Lambda runtime dotnetcore1.0 supports.
Apologies If this seems like a very basic query, I am very new to programming and IT in general(6mths).
Any help you can provide would be greatly appreciated.
Steve
The text was updated successfully, but these errors were encountered: