5 ms·

I completely agree, especially having just come from working with Azure Functions. This likely also applies to other runtimes, but definitely for dotnet, you ca

I completely agree, especially having just come from working with Azure Functions. This likely also applies to other runtimes, but definitely for dotnet, you can run all Functions in a solution locally via the default F5 debugging feature in Visual Studio. Stellar developer experience.

flyinglizard 6y ago
It’s astonishing how entrenched is the HN type in AWS that this no one said it before. P.S you can even attach the VS debugger to the live, deployed remote function and get full debugging (although quite slow). Don’t forget to deploy with the Debug (rather than Release) profile if you wanna do that. Breakpoints and all!
Arnavion 6y ago
And even if you're on Linux, there is a VSCode addon that is equivalent [1]. And even if you can't / don't want to use VSCode or the addon, you can download and run the Functions host yourself via the `func` tool [2]. (The latter is what I do for my own Functions.) One caveat with these options is that the Function won't get a Managed Service Identity since it's running locally, so if you have code that relies on an MSI you'll have to create a Service Principal and make your code support SPs too. Apart from that, the beahvior of the Function running locally or in the cloud should be identical. [1]: https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions https://marketplace.visualstudio.com/items?itemName=ms-azure... [2]: https://github.com/Azure/azure-functions-core-tools/releases https://github.com/Azure/azure-functions-core-tools/releases Azure.Functions.Cli.linux-*