Incompatibility with dbatools due to dll version differences.

[ArnoldLieberman-CoT]

Since we have started using dbatools, we have battled to get them to coexist. The problem is that sqlserver and dbatools ship with different versions of the dlls. For example, the latest available version of sqlserver - 22.4.5.1 ships with Microsoft.Data.SqlClient.SNI.dll version 5.1.1.0 (from 2023), whereas dbatools 2.7.13 is shipping with version 6.02.0.
So far, we have overwritten the DLLs in dbatools for fear of breaking sqlserver cmdlets, but this seems rather perverse and means that every time a new version of either module is released we have to repair the installation.
Is there a reason why the official sqlserver module should be using old DLLs?

[Matteo-T]

@ArnoldLieberman-CoT - nice timing!

I've started the work to move the module to depend on these 2 packages:

• SMO 180.13.0 (Assembly version: 18.0.0.0)
• MDS 6.1.3 (AssemblyVersion 6.0.0.0)

I do not have an ETA: the main unknown is that I do not want to break the interoperability with the Az.* modules and, sadly, those are using really old version of Azure.* packages...

I may end up pushing out a "preview" version of 23.0... so you guys can take a look and provide feedback.

[Matteo-T]

@potatoqualitee, FYI.

[ArnoldLieberman-CoT]

@Matteo-T this is good news! We are using AZ.* modules as well and it seems to behave, but of course this is only for the limited range of functions that we are using.