AzureFunctionsIntroduction

This is Sample project for Azure Functions. May this repository help you understand Azure Functions better.

I strongly recommend you to use v2 samples. v1 and csx are limited and obsolated.

What you can know

Please refer v2/.

More Reference

| Reference | Description | | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | | Blog post - tech.guitarrapc.com | Blog post for AzureFuncitons by repository owner. | | Azure/Azure-Functions | AzureFunctions official repo. You may find where to report Issue, Feature Requests, Questions and Help. | | Microsoft Azure WebJobs SDK Quick Reference | Web Job SDK cheat sheet. |

Precompiled functions reference

Refer many samples and demo.

https://github.com/Azure/Azure-Functions/wiki/Samples-and-content

Following additional tips will be useful for first step.

| Description | Screenshot | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | | VS2017 Update3 and higher is required for v2. | | Use v2 precompile function when you want to gain more faster execution and IDE compile, debug benefits. | | Unfortunately .csx is not yet match friendly for VS Debugging. It will not detect compile error and less intellisense at all.<br/> Therefore you will find .csx will cause compile error on Function App portal so often. If you feel it reduce your efficiency, then use precompile instead. | | There are several way for local debug with post/get request, LinqPad, PowerShell, curl and others. I use PostMan Chrome extensions heavily when local debugging and remote debugging. | |

Recommend Azure Functions settings for stability and efficiency

These settings are my recommendation with using AzureFunctions.

| Description | Screenshot | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Use zipdeploy integration with Run From Package to prove deploy atomic. PackageDeploy offers blue/green whole function deployment. <br/>In other words WebDeploy, ZipDeployment will not remove old name functions.<br/>You should consider using package deploy as possible as you can, and zip deploy is good PUSH Deploy option. | Announcing zipdeploy integration with Run From Package #110 | | Concider to select Dynamic Service Plan if possible. <br/>This will bring you best cost efficiency and scalability. | | | Keep your Azure Functions Runtime version up-to-date. Actually there's no meaning concider downtime because apply will be done in just a seconds. | <br/> | | Keep Function App Platform 32bit (don't change to 64bit) | | | Do not run out memory, add Dynamic Memory if needed! Default 128MB will be run out easiry. Upgrade to 256MB or higher as your app requires.<br/> Dynamic Plan pricing is relates to Memory size, but less meanful to concider.<br/>AzureFunctions pricing is here. | | | Make sure your functions memory comsumptions will be less than 1536MB. [This is limiation of Dynamic Service Plan](https://azure.microsoft.com/en-us/documen