Skip to content

Site Extension Resolution

Paul Batum edited this page Sep 19, 2018 · 2 revisions

In many scenarios, Azure Functions runs as a Site Extension. Functions is a little special however in that the site extension will load even in cases where the version was not specified appropriately (e.g. FUNCTIONS_EXTENSION_VERSION="").

For reference, here is the observed behavior as of September 2018:

Requested Version Resolved Version Notes
"~2" 2.0.12115.0 Resolves to the latest production build of V2
"~1" 1.0.11959.0 Resolves to the latest production build of V1
"" 2.0.12115.0 Resolves to the latest production build
"latest" 2.0.12115.0 Resolves to the latest production build
"fabioedition" 2.0.12115.0 Unrecognized version, so resolves to the latest production build
"1.0.99999" 1.0.11959.0 This version doesnt exist, so resolves to the latest production build matching major.minor
"~0.8" 2.0.12115.0 This version doesnt exist, but its also unable to resolve to a matching major.minor so it instead resolves to latest
"beta" 2.0.12115.0 Would resolve to a more recent pre-release version if it existed

Learn

Azure Functions Basics

Advanced Concepts

Dotnet Functions

Java Functions

Node.js Functions

Python Functions

Host API's

Bindings

V2 Runtime

Contribute

Functions host

Language workers

Get Help

Other

Clone this wiki locally