Comments
Sort by recent activity
The "RG_UseExecuteStatementsInPackageScript" workaround seems to be doing the trick for now. The version of the plugin we're using with TFS doesn't let us specify which version to use so as a second step we're going to look into updating the plugin so we can do that. The much bigger issue is that this is the second breaking change we've run into recently (see https://forum.red-gate.com/discussion/comment/156277#Comment_156277) - specifically using an older version is okay but it worries us that new versions are being released with these major issues. / comments
The "RG_UseExecuteStatementsInPackageScript" workaround seems to be doing the trick for now. The version of the plugin we're using with TFS doesn't let us specify which version to use so as a seco...
The "RG_UseExecuteStatementsInPackageScript" workaround seems to be doing the trick for now. The version of the plugin we're using with TFS doesn't let us specify which version to use so as a second step we're going to look into updating the plugin so we can do that. The much bigger issue is that this is the second breaking change we've run into recently (see https://forum.red-gate.com/discussion/comment/156277#Comment_156277) - specifically using an older version is okay but it worries us that new versions are being released with these major issues. / comments
The "RG_UseExecuteStatementsInPackageScript" workaround seems to be doing the trick for now. The version of the plugin we're using with TFS doesn't let us specify which version to use so as a seco...
The "RG_UseExecuteStatementsInPackageScript" workaround seems to be doing the trick for now. The version of the plugin we're using with TFS doesn't let us specify which version to use so as a second step we're going to look into updating the plugin so we can do that. The much bigger issue is that this is the second breaking change we've run into recently (see https://forum.red-gate.com/discussion/comment/156277#Comment_156277) - specifically using an older version is okay but it worries us that updates are coming out broken. / comments
The "RG_UseExecuteStatementsInPackageScript" workaround seems to be doing the trick for now. The version of the plugin we're using with TFS doesn't let us specify which version to use so as a seco...
In our case we're seeing this error using TFS which installs/uses the ReadyRoll.MSBuild NuGet package. According to our build logs a few days ago we were getting ReadyRoll.MSBuild.3.0.19073.6043 and everything worked fine. Today we're getting ReadyRoll.MSBuild.3.0.19077.6044 which has this error. Shouldn't a newer version be okay? We haven't done anything manually - this is just a new package that is automatically being provided by NuGet via the TFS add-on. I don't see the 3.0.19073.6043 version on NuGet anymore - did it get removed? I'm guessing it had a newer version of SQL Compare than what is in the current version and since we had builds/deploys using that version we're getting this error now that the older version is being used. On a dev system I deleted everything in __SchemaSnapshot and that got around it but I'd rather not do that for all our databases/environments. / comments
In our case we're seeing this error using TFS which installs/uses the ReadyRoll.MSBuild NuGet package.According to our build logs a few days ago we were getting ReadyRoll.MSBuild.3.0.19073.6043 and...
I did some digging and the SQL Compare version definitely changed. Here are the versions of RedGate.SQLCompare.Engine.dll in the various versions: - 3.0.19059.5510 had 13.7.3.9474 - 3.0.19073.6043 had 13.7.5.9770 - 3.0.19077.6044 has 13.7.3.9474 I'm guessing 3.0.19073.6043 had the new version of SQL Compare accidentally (or it had a bug) and it was yanked once someone realized and it was replaced with 3.0.19077.6044 that had the old version. You can't do that! Now any databases done with the 3.0.19073.6043 version will have that error. / comments
I did some digging and the SQL Compare version definitely changed. Here are the versions of RedGate.SQLCompare.Engine.dll in the various versions:- 3.0.19059.5510 had 13.7.3.9474- 3.0.19073.6043 h...
Is it going to be included in Visual Studio 2019 Enterprise like it was for 2017? / comments
Is it going to be included in Visual Studio 2019 Enterprise like it was for 2017?