Closed gabrielweyer closed 1 week ago
I have the same problem with the same versions of .NET and Azure Function Core Tools on my Mac.
Any luck funding solution to this anyone?
same here on Mac M1 with OSX, did anyone found any solutions
same here
Thanks @gabrielweyer We will investigate and share an update on this thread. .
Same here
Same here with azure-functions-core-tools@4/4.0.5907.
Found a workaround which is working for me on MacOS:
chmod +x /usr/local/Cellar/azure-functions-core-tools@4/4.0.5907/in-proc8/func
I also updates this, not sure if this is required for the workaround:
`
`
Using chmod on in-proc8/func helped get past the permissions problem. However, my visual studio code fails to attach.
Now that it compiles and runs, how do you debug?
@kshyju I saw your PR and I was able to fix the permissions problem as well using chmod +x
, but the function never starts now. When I use func host start
I don't get any error message it just exits execution:
When I start the debugger (f5), it builds, but the nothing happens until I get a timeout error saying: "Failed to detect running Functions host within 60"seconds. You may want to adjust the "azureFunctions.pickProcessTimeout" setting."
This behavior is even happening with new functions I created to test .net8 using the in-process model
I have Sonoma 14.5 macOs and I'm using:
@joserhonFA i have exactly the same behavior. i got it to build successfully using chmod but i get exactly the same result and output. Like a simple build only.
@joserhonFA i have exactly the same behavior. i got it to build successfully using chmod but i get exactly the same result and output. Like a simple build only.
- .NET SDK 8.0.400 (latest)
- Azure Function Core Tools (4.x, latest, clean download and installed)
- MacBook Pro, M3, Sonoma
what worked for me was changing the local.settings.json file. Try having only { "IsEncrypted": false, "Values": { "FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated" } }
@Doo-Santi We want to run the functions as „in-process“ (dotnet). Using your settings will run the functions in „isolated“ mode (dotnet-isolated). I will try it anyway, to confirm it still works in isolated mode. Thanks!
@joserhonFA i have exactly the same behavior. i got it to build successfully using chmod but i get exactly the same result and output. Like a simple build only.
- .NET SDK 8.0.400 (latest)
- Azure Function Core Tools (4.x, latest, clean download and installed)
- MacBook Pro, M3, Sonoma
what worked for me was changing the local.settings.json file. Try having only { "IsEncrypted": false, "Values": { "FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated" } }
This doesn't work. My function use the in-process model and I migrated to .net8 but still using the in-process model
I got it working for me, its a very inconvenient workaround but it works. Maybe it helps anybody in the meantime. I am using a MacBook Pro M3, Sonoma 14.3
cd your-dev-folder
gh repo clone Azure/azure-functions-core-tools
cd azure-functions-core-tools
dotnet publish src/Azure.Functions.Cli/Azure.Functions.Cli.csproj -f net8.0 --runtime osx-arm64 --output /tmp/cli
cd your-functions-project-root
/tmp/cli/func start
I tried the suggested workaround on my MacBook Pro M2 Somona 14.6.1
It worked, I started 'tmp/cli/func start' then used the command pallet to "Debug: Attach to .Net 5+ or .NET core process" and selected the running "func" application.
To make debugging easier, I updated my Visual Studio Code Configuration and set the "Azure Function Func Cli Path" setting to "/tmp/cli/func". Visual Studio Debug with then work from "Run/Start Debugging" menu.
When I run
func start
I get the below error:Steps taken:
func init MyProjFolder --worker-runtime dotnet
cd MyProjFolder/
func new --template "Http Trigger" --name MyHttpTrigger
I added
FUNCTIONS_INPROC_NET8_ENABLED
tolocal.settings.json
:I updated the project to target .NET 8:
I'm able to run an in-process .NET 8 on Windows using the Azure Function Core Tools and on a Windows Function App.