.azurefunctions about azure-functions-dotnet-worker HOT 2 CLOSED

The folder naming with "." in .azurefunctions is intentional. This is a common pattern for folders which are system or tool owned. We will not be renaming or changing this folder name.

from azure-functions-dotnet-worker.

Apologies for the delay. I would argue its not a common pratice for output release builds but if your not willing to adjust the output naming for whatever reason, i would then suggest it get documented appropriately to ensure everyone knows for their own CICDs etc, if they are using any form of compression to get the release build up into Azure, they need to specifically put your "." named folder in manually.

From my own personal opinion, i'm not to sure why your creating more friction in Azure Functions between the clients wanting to use it and the future development of it. Surely, making it as easy to use as possible is the main goal of the product, to encourage future spending by clients, whereas this decision and a couple of others since the worker isolated model seem to be in the absolutely opposite direction, harder for clients and causing issues for existing clients.

from azure-functions-dotnet-worker.