I have a unit test database project from VS 2015. Now I am testing VS 2017 RC.
There is a build conflict with the build Microsoft.Data.Tools.Schema.Sql.UnitTesting, and I'm not sure how to solve it. GAC has version 15.0 of this assembly. As part of the SSDT VS 2017, version 15.1 is available, but not in the GAC.
I tried redirecting the assembly in app.config, but that didn't help.
I tried to specifically browse the folder C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\Microsoft\SQLDBand select the assembly there as a link. However, he returned to the GAC assembly. He continued to do this even when I set Specific Version = True in the project properties.
I already deleted the old SSDT folder from the Reference Paths project property and pointed it to the 2017 location.
I had a similar build issue with Microsoft.Data.Tools.Components, but it was solved by specifying Specific Version = False (oddly enough ...) in the project properties.
If I remove the link from the project, the project builds, but warns that assembly version 15.0 cannot be found. In this case, the tests are even performed and pass. This continues only until the solution is open. When I close it and open it again, the "bad" links will again appear in the "Links" list.
EDIT . I ran asmspy and found some conflicts between 2.0 and 4.0 versions of system assemblies, including mscorlib and System.Data. On version 2.0, everyone refers to Microsoft.VisualStudio.QualityTools.UnitTestFrameworkversion 10.0. I updated these links to 10.1, but this version still references version 2.0 of these assemblies. I do not know if this is / is relevant.