#CREATE AZURE FUNCTION IN VISUAL STUDIO CODE PYTHON INSTALL#
They depend on a manually created function.json file to define the bindings and can install the appropriate extension packages based on the bindings. C# script functions are more like the javascript functions. But the extension templates now drive you to C# project functions and there’s a big difference.
Previously, I’d worked with C# script functions (.csx) which is the same as what you use when you work directly in the portal. Having revisited the docs enough times to finally notice some key information, I realize why the experience has changed with the extension working with C#.
But I’m so often on my MacBook and love using VS Code so I am going down this path with C# anyway. I’ve been using the version 2 APIs for a while so I’m not talking (well, writing) about that change from v1 to v2 here but the change in the experience using the Azure Functions extension.Īlso notable is that the Azure Functions team actually recommends using Visual Studio for building C# based apps and VS Code for JavaScript. I’ve also written about creating Azure Functions with VS Code in MSDN Magazine but again, this has changed since I wrote about it.
I should also state that for the past year or so I have focused on writing my functions with JavaScript just because I like to mix things up a bit and it also makes it easier to share Azure Functions with devs who are not. The latest shift threw me for a loop so I thought I would document some of it for those who may not have started yet. I’ve been using the Azure Functions for Visual Studio Code for some time now and they continue to evolve in great ways.
0 kommentar(er)
