Consider avoding DacFX package reference

[ErikEJ]

Related to an existing integration?

Yes

Existing integration

SqlProjects

Overview

DacFX carries a lot of dependencies that interferes with the AppHost dependencies (MsBuild related)

Usage example

Not a new feature, but we could use .NET 10 one-shot execution of Microsoft.Sqlpackage and remove the DacFX reference from DacpacDeployer

dnx Microsoft.SqlPackage --yes -- /a:Publish ....

Breaking change?

No

Alternatives

Hacky file removals

Additional context

See #949

Help us help you

Yes, I'd like to be assigned to work on this item

[ErikEJ]

@aaronpowell @jmezach Thoughts?

[aaronpowell]

Would you make the call to dnx an aspire resource?

How would we handle support for net8.0 and net9.0, as dnx might not be present on the machine? Would we have to do different assemblies?

[ErikEJ]

@aaronpowell No, just call the dnx command via the shell, instead of using DacFX APIs like we do today. We can do this only for .NET 10, maybe just with conditional compilation (so multiple assemsblies) - but do we need to support .NET 9 and .NET 8 still?

[ErikEJ]

Investigated this, it is not feasible

[aaronpowell]

do we need to support .NET 9 and .NET 8 still?

yeah, both are in support and have aspire support so we should continue to support them here too.