Open TylerLeonhardt opened 6 years ago
a workaround is to use publish, something like:
dotnet publish src/Azure.Functions.Cli/Azure.Functions.Cli.csproj --runtime osx-x64 --output /tmp/cli
# then do
/tmp/cli/func start
I encountered this issue on Windows also. I got it going by creating a workers folder in %userprofile%.nuget\packages\microsoft.azure.webjobs.script\2.0.12246\lib\netstandard2.0\workers In this folder, I then copied the content for a nodejs worker (I was trying to run a node function). I created a folder called Microsoft.Azure.Functions.NodeJsWorker and copied the content of the pkg folder when you run the package script in the nodejsworker repo.
On a mac with macOS 10.13 I am unable to follow the CONTRIBUTING.md guide to get a local build working.
Steps:
dotnet restore
cd src/Azure.Functions.Cli; dotnet build
mkdir /tmp/testFunctions; cd /tmp/testFunctions
dotnet run --project /path/to/azure-functions-core-tools/src/Azure.Functions.Cli init --worker-runtime node
dotnet run --project /path/to/azure-functions-core-tools/src/Azure.Functions.Cli new -l js -t HttpTrigger -n TestHttpTrigger
NOTE: everything works fine... until
dotnet run --project /Users/tyler/Code/CSharp/azure-functions-core-tools/src/Azure.Functions.Cli start
which gives me:
Note the:
I inspected this package to find:
No workers folder... not sure if that's expected.
Any thoughts?