Binding fails with target frameworks netcoreapp 2.1 and 2.2
See original GitHub issueThis package works fine when I target netcoreapp2.0. But when I target anything above that I get
Microsoft.Azure.WebJobs.Host: Error indexing method 'UploadImage'. Microsoft.Azure.WebJobs.Host: Cannot bind parameter 'cosmosDbClient' to type ICosmosDbClient. Make sure the parameter Type is supported by the binding. If you're using binding extensions (e.g. Azure Storage, ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. builder.AddAzureStorage(), builder.AddServiceBus(), builder.AddTimers(), etc.).
Issue Analytics
- State:
- Created 4 years ago
- Comments:10
Top Results From Across the Web
ASP.NET Core - 2.1 to 2.2 Issue
I have an ASP.NET Core Project that I need to update the Target Framework from 2.1 to 2.2 After changing the Target Framework,...
Read more >NET Core 2+ Version Binding · Issue #43525 · dotnet/runtime
A given SDK supports a fixed set of target frameworks. It is an error to target a framework outside that set. The SDK...
Read more >Running .NET Core Apps on a Framework other than ...
It fails to run due to the missing .NET Core 2.1 runtime. Notice that the error message is pretty helpful and shows what...
Read more >NETSDK1138: The target framework is out of support
NETSDK1138 indicates that your project targets a version of the framework that is out of support. The full error message is similar to...
Read more >Please stop lying about .NET Standard 2.0 support!
This post is a bit of a rant about an issue I've been fighting against more and more recently: NuGet packages lying about...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
check if the package you deploy have non-empty
extensions.json
file. If not, update functions sdk to 1.0.26.Not sure if this is will work, but try separate code with extensions into a library that function app will depend upon.