This is super hacky, but just wanted to leave the notes somewhere reusable that isn't official documentation. This isn't "recommended", but it is possible. :)
- Create your Functions via the Azure Functions portal UX is the easiest way. Otherwise, just follow the file format rules on the Azure Functions located here.
- Download them via your scm site -
{function app name}.scm.azurewebsites.net-> DebugConsole ->cd ./site-> click on the "download" button forwwwroot - Open Visual Studio, create a new Website, choose your unzipped wwwroot folder.
- Now you should see all your Functions in a directory in your Visual Studio. You can edit them here. etc.
- To Publish - Just right-click->publish on the project, choose an existing Web App (even though it's a function app, it speaks Web App apis, so it shows up here). Then publish with your changes. If might fail, just click on the "App Service Publishing" box at the bottom of VS and click "publish" from there. That should work.
- You need App Settings for various secrets/connection strings. These can't be modified except via Azure API calls. The best is to do this via the portal still. You can update via an ARM template if you need to do something locally.
- You cannot run locally, easily. You can potentially download the script runtime locally and set up local env variables for the secrests, etc. Find more about that here - https://github.com/Azure/azure-webjobs-sdk-script/wiki
This is clearly not great, but it's possible. Feel free to leave comments here or tweet @crandycodes with any feedback on the tooling story. We'll be getting some better stuff rolling around tooling very soon. :)