You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-bindings-register.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,13 +20,13 @@ Extension bundles allow non-.NET apps to use binding extensions without having t
20
20
21
21
Extension bundles add a predefined set of compatible binding extensions to your function app. Extension bundles are versioned. Each version contains a specific set of binding extensions that are verified to work together. Select a bundle version based on the extensions that you need in your app.
22
22
23
-
When you create a non-.NET Functions project from tooling or in the portal, extension bundles are already enabled in the app's *host.json* file.
23
+
When you create an Azure Functions project from a non-.NET template, extension bundles are already enabled in the app's *host.json* file.
24
24
25
25
You define an extension bundle reference in the *host.json* project file by adding an `extensionBundle` section, as in this example:
The following table lists the currently available version ranges of the default *Microsoft.Azure.Functions.ExtensionBundle* bundlesand links to the extensions they include.
29
+
The following table lists the currently available default *Microsoft.Azure.Functions.ExtensionBundle* bundles, defined using version ranges and with links to the extension definitions for the bundle.
30
30
31
31
| Bundle version | Version in host.json | Included extensions |
32
32
| --- | --- | --- |
@@ -45,12 +45,16 @@ For a complete list of extension bundle releases and extension versions in each
45
45
46
46
## Explicitly install extensions
47
47
::: zone pivot="programming-language-csharp"
48
-
For compiled C# class library projects ([in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md)), you install the NuGet packages for the extensions that you need as you normally would. For examples, see either the [Visual Studio Code developer guide](functions-develop-vs-code.md?tabs=csharp#install-binding-extensions) or the [Visual Studio developer guide](functions-develop-vs.md#add-bindings). See the [extension bundles release page](https://github.com/Azure/azure-functions-extension-bundles/releases) to review combinations of extension versions that are verified compatible.
48
+
For compiled C# class library projects ([in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md)), you install the NuGet packages for the extensions that you need as you normally would. For more information, see the [Visual Studio Code developer guide](functions-develop-vs-code.md?tabs=csharp#install-binding-extensions) or the [Visual Studio developer guide](functions-develop-vs.md#add-bindings).
49
+
50
+
See the [extension bundles release page](https://github.com/Azure/azure-functions-extension-bundles/releases) to review combinations of extension versions that are verified to be compatible.
49
51
::: zone-end
50
52
::: zone pivot="programming-language-python,programming-language-java,programming-language-javascript,programming-language-typescript,programming-language-powershell,programming-language-other"
51
-
When you can't use extension bundles you instead must manually install any required binding extensions in your local project. The easiest way to generate the correct C# project is to use Azure Functions Core Tools. For more information, see [func extensions install](functions-core-tools-reference.md#func-extensions-install).
53
+
There are cases when you can't use extension bundles, such as when you need to use a specific prerelease version of a specific extension. In these rare cases, you must manually install any required binding extensions in a C# project file (*extensions.csproj*) that references the specific extensions required by your app.
54
+
55
+
The easiest way to create this C# file in your local project is by using Azure Functions Core Tools. For more information, see the [func extensions install](functions-core-tools-reference.md#func-extensions-install) command, which generates this project for you.
52
56
53
-
For portal-only development, you need to manually create an extensions.csproj file in the root of your function app. To learn more, see [Manually install extensions](functions-how-to-use-azure-function-app-settings.md#manually-install-extensions).
57
+
For portal-only development, you need to manually create an extensions.csproj file in the root of your function app in Azure. To learn more, see [Manually install extensions](functions-how-to-use-azure-function-app-settings.md#manually-install-extensions).
0 commit comments