Activity overview
Latest activity by scottw_cm
Hi Tianjiao, The full version is 3.3.19206.9626 for SqlChangeAutomation.dll - let me know if you were looking for something different. This is a local install of SQL Server, and the user account has the sysadmin role in SQL. Regards, Scott / comments
Hi Tianjiao,The full version is 3.3.19206.9626 for SqlChangeAutomation.dll - let me know if you were looking for something different.This is a local install of SQL Server, and the user account has ...
Powershell Commandlets crash on Invoke-DatabaseBuild
When running Invoke-DatabaseBuild, I'm getting the below error. This machine is fresh installed using SQL Toolbelt which contained SQL Change Automation Powershell 3.3. Please advise how I should p...
The above article is unrelated to the issue at hand. Apologies, let me clarify the repro steps: 1) From Visual Studio, create a new .NET Core Application - doesn't matter if it's a console or web app. Give it a name and save it. 2) Navigate to the solution folder from command prompt and execute: dotnet build <solutionfile> The project will build successfully. 3) From Visual Studio again, add a SQL Change Automation project to the same solution. 4) Follow the usual steps of creating a baseline script from a test database and deploying it to a local development database. Confirm that it builds from Visual Studio with <ctrl>+B (it should build fine) 5) Navigate to the solution folder from command prompt and execute: dotnet build <solutionfile> Expected: The project will build successfully. Actual: The project build will fail with the following error: error MSB4019: The imported project "C:\Program Files\dotnet\sdk\2.1.500\SqlChangeAutomation\SqlChangeAutomation.Data.Schema.Ssdt.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. As "dotnet build" is the method to build solutions with .NET Core (instead of msbuild as on the .NET Framework), this will likewise cause the entire project to fail to build on a build server, hence the importance of supporting SCA on dotnet.exe builds. This error prevents a .NET Core project from using SQL Change Automation at all without using multiple solution files or breaking up the build into separate steps (one for each top-level project). Note the above repro steps are assuming .NET Core 2.1 is used, but I suspect any version of .NET Core would encounter the same issue as the tooling is different from standard .NET Framework. Thanks, Scott / comments
The above article is unrelated to the issue at hand.Apologies, let me clarify the repro steps:1) From Visual Studio, create a new .NET Core Application - doesn't matter if it's a console or web app...