Skip to content

Commit e74fe5d

Browse files
committed
Update the binding extensions article with language pivots
1 parent 08e5fdb commit e74fe5d

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

articles/azure-functions/functions-bindings-register.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,13 +20,13 @@ Extension bundles allow non-.NET apps to use binding extensions without having t
2020

2121
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.
2222

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.
2424

2525
You define an extension bundle reference in the *host.json* project file by adding an `extensionBundle` section, as in this example:
2626

2727
[!INCLUDE [functions-extension-bundles-json](../../includes/functions-extension-bundles-json.md)]
2828

29-
The following table lists the currently available version ranges of the default *Microsoft.Azure.Functions.ExtensionBundle* bundles and 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.
3030

3131
| Bundle version | Version in host.json | Included extensions |
3232
| --- | --- | --- |
@@ -45,12 +45,16 @@ For a complete list of extension bundle releases and extension versions in each
4545

4646
## Explicitly install extensions
4747
::: 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.
4951
::: zone-end
5052
::: 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.
5256

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).
5458
::: zone-end
5559
## Next steps
5660
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)