Hello Vijay Pratap Singh
Azure Functions where the build process creates a nested bin
folder. This can happen due to certain build configurations or project settings
This issue affects many scenarios with configuration files. Only when using Azure Functions, config files tagged with CopyToPublishDirectory
are copied to bin/output
but the assembly execution path is bin/output/bin
.
In other words:
- classic .NET app:
assembly execution path
==config files path
- Azure functions:
assembly execution path
!=config files path
https://github.com/Azure/azure-functions-vs-build-sdk/issues/518
To resolve the issue try to make the file as Copy Always
:
<None Update=
In VS, Click on the file > Properties
> Change Copy to Output Directory
> Copy Always
.
https://stackoverflow.com/questions/66317440/azure-function-create-folders-in-the-bin-folder