Configuration for trimmed exe including SqlClient

[jods4]

I understand MS.Data.SqlClient does not support trimming yet.
Could the team share a build configuration that works in .NET 8.0 to include SqlClient untrimmed into an exe that is otherwise trimmed?

My goal is to publish a CLI tool that is self-contained -- and obviously trimmed for size.

Since I updated to latest MS.Data.SqlClient and .NET 8.0, no configuration I tried to exclude SqlClient from trimming works.
The only setup that works is completely disabling trimming, and insead of being ~30Mo the self-contained executable is ~180Mo now. That's terrible for a CLI tool.

Most things I tried usually end up in a TypeLoadException with "Unable to load DLL 'Microsoft.Data.SqlClient.SNI.dll'".

[ErikEJ]

https://github.com/0xced/Chisel

[jods4]

Thanks! This project is interesting to remove bits that shouldn't be there in the first place, but that's not really my question.

I'm ok (for now) with including all of MS.Data.SqlClient in my application, without any kind of trimming for this lib.

I'd like to still be able to use the dotnet trimming feature for the rest of my app.

There are documented options here:
https://learn.microsoft.com/en-us/dotnet/core/deploying/trimming/trimming-options?pivots=dotnet-8-0

And I've tried to go back to the previous default of partial for TrimMode, I've tried rooting MS.Data.SqlClient with TrimmerRootAssembly but it didn't work.

I'd like an example of a csproj configuration where .net 8 trimming works in a project using SqlClient (understanding that SqlClient itself can't be trimmed, but the rest should).

[Numpsy]

Hi,
Did you ever get anywhere with getting this to work?
I've been trying to get a trimmed self contained app working on .NET 9 and getting TypeInitializationExceptions when it does some SSL setup in TDSParser, and as you say, setting trim mode and rooting the SqlClient assembly doesn't help.

Marking System.Private.CoreLib as a root assembly does seem to help, but I haven't worked out exactly what it is that's getting trimmed when it shouldn't yet

[dlosch]

if this is still open (which I doubt).

Disclaimer: Officially afaik, it's not supported, so I wouldn't recommend.

For basic SqlClient functionality with trimming or aot, based on my experience you need

• add an explicit nuget reference to
  <PackageReference Include="System.Configuration.ConfigurationManager" /> (your app will work without it, but it will raise handled exceptions in the background if you don't)

a) on linux:
TrimmerRootDescriptor with (<TrimmerRootDescriptor Include="rd.xml" />)

<linker>
  <assembly fullname="System.Configuration.ConfigurationManager">
    <type fullname="System.Configuration.ClientConfigurationHost" preserve="all"/>
  </assembly>
</linker>

Note: this is optional. If you don't do this, the application will internally throw exceptions (which will be caught by the sqlclient code), but it will work.

b) on windows (<TrimmerRootDescriptor Include="rd.xml" />)

<linker>
  <assembly fullname="System.Configuration.ConfigurationManager">
    <type fullname="System.Configuration.ClientConfigurationHost" preserve="all"/>
  </assembly>
  <assembly fullname="System.Private.CoreLib">
    <type fullname="System.StubHelpers.InterfaceMarshaler" preserve="all"/>
  </assembly>
</linker>

(on windows it does use the SNI dll)

Note: I didn't play around with the "preserve=all". I only got rid of exceptions.

I use SqlClient and trimmed and aot builds on linux-x64, not in production, with SqlConnection/SqlCommand and basic auth (with TLS).

You will get (handled) exceptions: System.NullReferenceException at Microsoft.Data.SqlClient.SqlClientEventSource.OnEventCommand
and if you use OpenTelemetry for SqlClient, in AOT this will not give full fidelity (it will work though).