Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify FunctionsPreservedDependencies and FunctionsSkipCleanOutput #77460

Closed
wants to merge 3 commits into from
Closed

Clarify FunctionsPreservedDependencies and FunctionsSkipCleanOutput #77460

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
438b9fb
Clarify FunctionsPreservedDependencies and FunctionsSkipCleanOutput
fowl2 Jun 25, 2021
468001a
Update functions-develop-vs.md
fowl2 Jun 25, 2021
3b4a10d
Update functions-develop-vs.md
fowl2 Jun 25, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions articles/azure-functions/functions-develop-vs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,20 @@ When building an Azure Functions project, the build tools optimize the output so
</ItemGroup>
```

> [!NOTE]
> Support for `FunctionsPreservedDependencies` was [added](https://github.com/Azure/azure-functions-host/pull/6849) in [Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator 1.2.1](https://github.com/Azure/azure-functions-host/releases/tag/emg-v1.2.1), which was first included in Microsoft.NET.Sdk.Functions version [3.0.12](https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions/3.0.12).

This output optimization step can be completely disabled with the `FunctionsSkipCleanOutput` property.

```xml
<PropertyGroup>
<FunctionsSkipCleanOutput>true</FunctionsSkipCleanOutput>
</PropertyGroup>
```

> [!NOTE]
> `FunctionsSkipCleanOutput` was called `_FunctionsSkipCleanOutput` in older version of the build tools, including in Azure Functions v 1.x.

## Configure the project for local development

The Functions runtime uses an Azure Storage account internally. For all trigger types other than HTTP and webhooks, set the `Values.AzureWebJobsStorage` key to a valid Azure Storage account connection string. Your function app can also use the [Azure Storage Emulator](../storage/common/storage-use-emulator.md) for the `AzureWebJobsStorage` connection setting that's required by the project. To use the emulator, set the value of `AzureWebJobsStorage` to `UseDevelopmentStorage=true`. Change this setting to an actual storage account connection string before deployment.
Expand Down