In Azure Functions, we use Bindings as a way of connecting resources to our functions. We can use input and output bindings and the data from our bindings is provided to our Functions as parameters.
Bindings in .NET Isolated Project are different because they can't use the binding classes like IAsyncCollector. We also can't use the types inherited from SDKs like DocumentClient. Instead we have to rely on strings, arrays and POCOs (Plain Old Class Objects).
In this post, I'll explain what Bindings are in Azure Functions, How they currently work with in-process Functions and how for isolated functions, they work a little differently.
https://dev.to/willvelida/how-do-bindings-work-in-out-of-process-net-azure-functions-1o2
Bindings in .NET Isolated Project are different because they can't use the binding classes like IAsyncCollector. We also can't use the types inherited from SDKs like DocumentClient. Instead we have to rely on strings, arrays and POCOs (Plain Old Class Objects).
In this post, I'll explain what Bindings are in Azure Functions, How they currently work with in-process Functions and how for isolated functions, they work a little differently.
https://dev.to/willvelida/how-do-bindings-work-in-out-of-process-net-azure-functions-1o2