Skip to content

Commit b466dd9

Browse files
Minimum in-proc SDK for core tools
1 parent e89619a commit b466dd9

File tree

3 files changed

+39
-4
lines changed

3 files changed

+39
-4
lines changed

articles/azure-functions/functions-develop-vs.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -219,6 +219,13 @@ For a full list of the bindings supported by Functions, see [Supported bindings]
219219
220220
Azure Functions Core Tools lets you run Azure Functions project on your local development computer. When you press F5 to debug a Functions project, the local Functions host (func.exe) starts to listen on a local port (usually 7071). Any callable function endpoints are written to the output, and you can use these endpoints for testing your functions. For more information, see [Work with Azure Functions Core Tools](functions-run-local.md). You're prompted to install these tools the first time you start a function from Visual Studio.
221221
222+
::: zone pivot="in-proc"
223+
224+
> [!IMPORTANT]
225+
> Starting with version 4.0.6517 of the Core Tools, in-process model projects must reference [version 4.5.0 or later of `Microsoft.NET.Sdk.Functions`](https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions/4.5.0). If an earlier version is used, the `func start` command will error.
226+
227+
::: zone-end
228+
222229
To start your function in Visual Studio in debug mode:
223230
224231
1. Press F5. If prompted, accept the request from Visual Studio to download and install Azure Functions Core (CLI) tools. You might also need to enable a firewall exception so that the tools can handle HTTP requests.

articles/azure-functions/functions-dotnet-class-library.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -226,10 +226,13 @@ The following example shows the relevant parts of the `.csproj` files that have
226226
<AzureFunctionsVersion>v4</AzureFunctionsVersion>
227227
</PropertyGroup>
228228
<ItemGroup>
229-
<PackageReference Include="Microsoft.NET.Sdk.Functions" Version="4.4.0" />
229+
<PackageReference Include="Microsoft.NET.Sdk.Functions" Version="4.5.0" />
230230
</ItemGroup>
231231
```
232232

233+
> [!IMPORTANT]
234+
> Starting with version 4.0.6517 of the Core Tools, in-process model projects must reference [version 4.5.0 or later of `Microsoft.NET.Sdk.Functions`](https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions/4.5.0). If an earlier version is used, the `func start` command will error.
235+
233236
# [v1.x](#tab/v1)
234237

235238
```xml

articles/azure-functions/functions-run-local.md

Lines changed: 28 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,15 +55,15 @@ For help with version-related issues, see [Core Tools versions](#v2).
5555
In the terminal window or from a command prompt, run the following command to create a project in the `MyProjFolder` folder:
5656

5757
::: zone pivot="programming-language-csharp"
58-
### [Isolated process](#tab/isolated-process)
58+
### [Isolated worker model](#tab/isolated-process)
5959

6060
```console
6161
func init MyProjFolder --worker-runtime dotnet-isolated
6262
```
6363

6464
By default this command creates a project that runs in-process with the Functions host on the current [Long-Term Support (LTS) version of .NET Core]. You can use the `--target-framework` option to target a specific supported version of .NET, including .NET Framework. For more information, see the [`func init`](functions-core-tools-reference.md#func-init) reference.
6565

66-
### [In-process](#tab/in-process)
66+
### [In-process model](#tab/in-process)
6767

6868
```console
6969
func init MyProjFolder --worker-runtime dotnet
@@ -199,7 +199,27 @@ mvn clean package
199199
mvn azure-functions:run
200200
```
201201
::: zone-end
202-
::: zone pivot="programming-language-csharp,programming-language-javascript,programming-language-powershell,programming-language-python"
202+
::: zone pivot="programming-language-csharp"
203+
204+
### [Isolated worker model](#tab/isolated-process)
205+
206+
```
207+
func start
208+
```
209+
210+
### [In-process model](#tab/in-process)
211+
212+
```
213+
func start
214+
```
215+
216+
> [!IMPORTANT]
217+
> Starting with version 4.0.6517 of the Core Tools, in-process model projects must reference [version 4.5.0 or later of `Microsoft.NET.Sdk.Functions`](https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions/4.5.0). If an earlier version is used, the `func start` command will error.
218+
219+
---
220+
221+
::: zone-end
222+
::: zone pivot="programming-language-javascript,programming-language-powershell,programming-language-python"
203223
```
204224
func start
205225
```
@@ -513,6 +533,11 @@ If you must use a binding extension or an extension version not in a supported b
513533

514534
Major versions of Azure Functions Core Tools are linked to specific major versions of the Azure Functions runtime. For example, version 4.x of Core Tools supports version 4.x of the Functions runtime. This version is the recommended major version of both the Functions runtime and Core Tools. You can determine the latest release version of Core Tools in the [Azure Functions Core Tools repository](https://github.com/Azure/azure-functions-core-tools/releases/latest).
515535

536+
::: zone pivot="programming-language-csharp"
537+
<a name="in-process-minimum-version"></a>
538+
Starting with version 4.0.6517 of the Core Tools, in-process model projects must reference [version 4.5.0 or later of `Microsoft.NET.Sdk.Functions`](https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions/4.5.0). If an earlier version is used, the `func start` command will error.
539+
::: zone-end
540+
516541
Run the following command to determine the version of your current Core Tools installation:
517542

518543
```command

0 commit comments

Comments
 (0)