One of the most common sources of feedback we receive relate to .NET assembly resolution and loading issues in Azure Functions. The goal of this post is to help .NET developers avoid those problems, understand the current limitations, provide guidance on how to avoid or mitigate some of those issues, when possible, and go over some of the details on how this will be improved in the next version of Azure Functions.
In the following sections, we dive into the details of how things work today