Skip to content

Added documentation for build output settings #65127

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

Merged
merged 3 commits into from
Dec 17, 2020
Merged

Added documentation for build output settings #65127

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
31d31f7
Added documentation for build output settings
gzuber Oct 28, 2020
30a0b05
Removed mention of FunctionsSkipCleanOutput. Cleaned up language.
gzuber Oct 30, 2020
7559515
Cleaned up tone and voice
gzuber Dec 16, 2020
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
12 changes: 12 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 @@ -81,6 +81,18 @@ Visual Studio doesn't automatically upload the settings in local.settings.json w

Your code can also read the function app settings values as environment variables. For more information, see [Environment variables](functions-dotnet-class-library.md#environment-variables).

## Configure your build output settings

When building an Azure Functions project, the build tools will optimize the output so that only one copy of any assemblies that are shared with the functions runtime will be preserved. The result is an optimized build that saves as much space as possible. However, if you move to a more recent version of any of these assemblies in your project, the build tools might not know that these assemblies need to be preserved. In order to ensure that these assemblies are preserved during the optimization process, you can specify them in your function's .csproj file:

```xml
<ItemGroup>
<FunctionsPreservedDependencies Include="Microsoft.AspNetCore.Http.dll" />
<FunctionsPreservedDependencies Include="Microsoft.AspNetCore.Http.Extensions.dll" />
<FunctionsPreservedDependencies Include="Microsoft.AspNetCore.Http.Features.dll" />
</ItemGroup>
```

## 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