Support for SqlClient v7

[SimonCropp]

just to start the ball rolling...

[SimonCropp]

any update on this?

[dvdstelt]

It was already added by automation and should be picked up when the next rotation group picks up these PRs and creates a release.

[tmasternak]

Hi @SimonCropp, to get more context, is this change going to unlock any features on your end? Are you blocked in using the v7 client in any way?

[ramonsmits]

Hi @SimonCropp, to get more context, is this change going to unlock any features on your end? Are you blocked in using the v7 client in any way?

@tmasternak see:

• Update dependency Microsoft.Data.SqlClient to v7 #1669 (comment)

I assume @SimonCropp is interested because of this as I know he has been active in the past on the Microsoft issue.

[SimonCropp]

@tmasternak

Are you blocked in using the v7 client in any way

we can update to v7 without NSB doing so. but there is some nervousness in the team about forcing NSBSql onto a new major when particular hasnt done an update+deployment, with all the regression testing that entails.

[tmasternak]

Hi @SimonCropp,

I can confirm that the client version 7.0.0 has been tested for compatibility with the transport:

• We ran our automated tests with and without opt-in features included
• Analyzed Microsoft's release notes
• Smoke tested with a sample

We can confirm that the transport works with version 7.0.0.

For now, we will not be releasing the new major version of the transport that will bump the minimal version range on the client SDK to 7.0.0. The work on that will be tracked under:

• https://github.com/Particular/NServiceBus.SqlServer/milestone/89