How the App Service team functions

Azure Functions 0.5 release & August portal update

We're happy to announce we've officially released Azure Functions host version 0.5 into our Public Preview, as well as some updates to our Portal experience. The host version does include several breaking changes, so please read the release notes before upgrading. We will also be updating our default version in create to ~0.5 as well, so new deployments that don't specify a version will be on the latest.

F# support now in preview

Thanks to the excellent work by the F# team including Don Syme and Tomas Petricek, we're happy to announce we finally support F# in a first-class fashion in Azure Functions. Previously, we just invoked your F# script via fsi. Today, it now running hot in our runtime, with support for input and output bindings. Note that this new F# experience is incompatible with the previous versions.

If you are familiar with the C# experience, you'll remember the TraceWriter. This is because we support all the same types that C# supports. We haven't finished updating the documentation yet, but we'll be soon updating the C# docs to be the .NET docs.

For those curious in how it was built, feel free to check out PR #577.

Other breaking changes & improvements

In addition to F# support, we have a few other breaking changes and notable improvements. You can read our full release notes on 0.5 release on GitHub.

Portal updates

We also have some large updates to the portal experience rolling out today. Below are some highlights:

Localization is now available for many languages

Tabs have all been moved to the left nav, rather than left and top. This change happened to improve usability in understanding Functions vs Function Apps.

Actions for certain output bindings on Integrate tab. We found it was common to copy+paste settings from an output binding to a new trigger, so we added a button to do it for you.

Dropdown pickers for connections – if you have an existing connection to Storage/etc., we'll show you those in a dropdown menu, rather than always having to choose from the picker blade (which can have LOTS of choices for large, shared subscriptions).

Documentation is now available in the Integrate tab. This will hopefully make it more obvious how to use the bindings when you add them/modify them, rather than knowing where in the main docs site to look.

You can now delete/rename files from the file explorer menu on the Develop Tab.

Better whitespace usage on Integrate tab

App Settings, Kudu, and Console now available from the Function App Settings menu, rather than having to jump through Advanced Settings.

What comes next?

With this release complete, we'll be starting our next wave of planning. We need and look forward to your feedback. You can submit general feedback on feedback.azure.com or, if you feel familiar with our host or portal, you can submit issues directly on GitHub (Host GitHub & Portal GitHub). Most of our planning happens on GitHub, so you can see things coming as they are in progress.

Feel free to ask questions below or reach out to us on Twitter via @AzureFunctions. We hope you have fun with the new changes. We're looking forward to seeing what you do!

Categories

Tags

Join the conversation

After updating to 0.5 source control binding seems to be gone, scripts are editable in the browser and there is message at the top “It looks like you don’t have a functions container. Select a subscription to create one: “.

The Function time version is an App Setting. If you go to Manage tab on your function you should be able to see an upgrade button. Or you can go to Function App Setting and then Configure App Setting, you soudl see list of app setting. The FUNCTIONS_EXTENSION_VERSION state the version you are currently using.