Emit DacFx and Database Reference Versions in Build Output
- Dominant language
- C#
- Stars
- 460
- Forks
- 29
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 7
Description
✨ Feature Request: Output DacFx and Database Reference Versions
**Is your feature request related to a problem? Please describe.**
I'm always frustrated when trying to troubleshoot database builds or deployments using dotnet build or sqlpackage, and I can't easily determine which version of DacFx or database references (e.g., master.dacpac) were actually used during the process. This makes it difficult to identify version mismatches across environments or diagnose issues with builds and deployments.
**Describe the solution you'd like**
I would like dotnet build (when building SDK-style .sqlproj) and sqlpackage (for deployment or script generation) to include the following in the standard output:
The version of Microsoft.SqlServer.DacFx being used (e.g., 170.0.94.3)
Possibly the version of Microsoft.Build.Sql
The versions of any referenced DACPACs (e.g., Microsoft.SqlServer.Dacpacs.Azure.Master v160.2.4)
This information could be printed by default or behind an optional verbosity flag (/v:normal or /v:detailed), and would dramatically improve traceability and troubleshooting.
Example:
```
DacFx version: 170.0.94.3
Reference: Microsoft.SqlServer.Dacpacs.Azure.Master v160.2.4
```
**Describe alternatives you've considered**
Note sure how else to get this information open to suggestions
I would expect this to end up in one of the build artifacts but wasn't able to find it
**Additional context**
This would be especially helpful in DevOps pipelines or Fabric deployments where validation of toolchain versions is critical. It would also help differentiate between breaking changes caused by SDK upgrades versus other deployment logic.
Contributor guide
Research direction
Start with the dotnet build path for SDK-style .sqlproj projects and the sqlpackage paths for deployment or script generation. Trace how standard output and verbosity are handled, then verify that the DacFx version and referenced DACPAC versions appear in the requested output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- build-system, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100