Home Original page

[Azure Functions] Improve local NuGet build script by lucaspimentel · Pull Request #8174 · DataDog/dd-trace-dotnet

@lucaspimentel

chatgpt-codex-connector[bot]

@lucaspimentel lucaspimentel added the AI Generated

Largely based on code generated by an AI or LLM. This label is the same across all dd-trace-* repos

label

Feb 7, 2026

@lucaspimentel lucaspimentel changed the title Improve Azure Functions NuGet build script [Azure Functions] Improve NuGet build script

Feb 7, 2026

@lucaspimentel

jcstorms1

andrewlock

@lucaspimentel lucaspimentel deleted the lpimentel/improve-azure-functions-nuget-build-script branch

February 10, 2026 04:38

@lucaspimentel lucaspimentel changed the title [Azure Functions] Improve NuGet build script [Azure Functions] Improve local NuGet build script

Feb 10, 2026

lucaspimentel added a commit that referenced this pull request

Feb 13, 2026 
## Summary of changes

- Use separate Nuke verbosity levels for download (`quiet`) vs build
(`normal`) targets
- Skip building `net461` in local dev script (commented out)
- Disable `CheckEolTargetFramework` warning

## Reason for change
After #8174 changed default verbosity to `quiet`, the package path
output was suppressed, making it harder to locate the generated `.nupkg`
file during local development.

## Implementation details

In `tracer/tools/Build-AzureFunctionsNuget.ps1`, split `$nukeVerbosity`
into two variables:
- `$nukeVerbosityDownload`: `verbose`/`quiet` for
`DownloadBundleNugetFromBuild`
- `$nukeVerbosityBuild`: `verbose`/`normal` for
`BuildAzureFunctionsNuget` (shows package path)

In `tracer/src/Datadog.AzureFunctions/Datadog.AzureFunctions.csproj`,
remove`CheckEolTargetFramework` so we inherit `false` from a parent
directory.

## Test coverage
Manually tested.