Closed AartBluestoke closed 1 year ago
NOTE: Unit tests fail here with the updated target DacPac with an index. The old DacPac passes all unit tests.
Removing the AdditionalDeploymentContributors allows the tests to pass, so it is something to do with the contributor.
Hi @AartBluestoke, thanks for spending time on this!
I have some concerns:
@t-johnson I've (perhaps temporarily) included the old sql package folder in the project - it however fails to load the framework build of the filter - I know we have an 'framework' targeted dll, but i don't know how to compile a filter version to target the 'old' version of sqlpackage (which is the one included in vs 2019, and is not listed on ) (the 'old' version that was there 15.0.4281.1 - not listed on https://learn.microsoft.com/en-us/sql/tools/sqlpackage/release-notes-sqlpackage - but appears to be a build number shortly before 18.1)
@AartBluestoke yeah no idea where that old version of SqlPackage came from. If we do want to have the integration tests run with the .NET 6 and the .NetFramework builds of SqlPackage, i would think it would be better to keep a version of SqlPackage that is mentioned on the MS page.
i checked out your changes - DacPac.refactorlog is mentioned but not included? we probably don't need this file at all?
@t-johnson
@t-johnson the specific problematic breaking change is at 19.0 - January 2022: you can't have the one DLL target both System.Data.SqlClient and Microsoft.Data.SqlClient
@t-johnson
fyi: Notes for sql package version ... Included in the repo above are two 162.0.52.1 versions.