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/extension-bundles.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Extension bundles add a predefined set of compatible binding extensions to your
19
19
20
20
When you create an Azure Functions project from a non-.NET template, extension bundles are already enabled in the app's `host.json` file.
21
21
22
-
## Defining an extension bundle reference
22
+
## Define an extension bundle reference
23
23
24
24
You define an extension bundle reference in the `host.json` project file by adding an `extensionBundle` section, as in this example:
25
25
@@ -59,7 +59,7 @@ Keep these considerations in mind when upgrading the extension bundle version us
59
59
+ Local project: extensions are updated locally when Core Tools starts, either from the `func start` command or when debugging in your development tools.
60
60
+ Function app: extensions are updated when you deploy the updated host.json file to your function app in Azure.
61
61
62
-
## Previewing extension bundles
62
+
## Preview extension bundles
63
63
64
64
Prerelease versions of specific binding extensions are maintained in a preview extension bundle: `Microsoft.Azure.Functions.ExtensionBundle.Preview`. You can use this preview extension bundle to take advantage of preview extensions and new behaviors in existing extensions before they reach general availability (GA).
0 commit comments