Open hirensharma opened 2 years ago
Same problem here. Any temp workarounds?
I found a workaround using the following configuration:
- name: myfunc
executable: func
args: start {pathtofolder}/Company.FunctionApp1.csproj -p 7071
workingDirectory: {pathtofolder}
bindings:
- port: 7071
protocol: http
Anyway there might be a much simpler solution, so still open for suggestions
Describe the bug
I have a couple of micro-services along with some Azure Functions (dotnet-isolated ones) and the Azure Function fails to run. I guess the command its using internally is dotnet run, whereas, the new function utilizes the command "func start" with the help of Azure Function Core Tools
To Reproduce
Further technical details