Activity overview
Latest activity by alovhaug
@DanC - from my standpoint, the Visual Studio MSBuild "Build Solution" step doesn't have to "work" for a build and deployment, it just shouldn't generate an error as it is doing now. As @PDQ is doing, we are using the supported Powershell add-on steps for the actual build and deployment. But my solution has both the SCA project AND other projects associated with the build altogether. I use the Visual Studio MSBuild "Build Solution" step in my pipeline to build all the other projects. I don't want to have to manage multiple solutions, and having extra build configurations is also a pain, especially if you suddenly have to make changes for a lot of solutions as @PDQ has to do. --Avonelle / comments
@DanC - from my standpoint, the Visual Studio MSBuild "Build Solution" step doesn't have to "work" for a build and deployment, it just shouldn't generate an error as it is doing now. As @PDQ is doi...
clopez said:
I am in the process to rollback to a previous version. https://download.red-gate.com/checkforupdates/SQLChangeAutomation/SQLChangeAutomation_4.4.22184.30843.exe [download.red-gate.com]
I'll be interested if this works, but also surprised. I was already at an older version. For what it is worth, I find it strange that the version of assembly Newtonsoft.Json in the MSBuild\SqlChangeAutomation\ folder is the same on my development computer as on my build computer, but while it builds fine on my development computer, I get this error on the build server. (It is a substantially newer version than 6.0.0.0, but it doesn't seem to be an issue locally. Hmmmm....) --Avonelle / comments
clopez said:
I am in the process to rollback to a previous version.https://download.red-gate.com/checkforupdates/SQLChangeAutomation/SQLChangeAutomation_4.4.22184.30843.exe [download.red-gate.c...
You are not alone. I just ran a build myself and am seeing this problem also. In my case, it is with Visual Studio 2019 not 2017, but yes otherwise the same error message. I really don't want to have to rework the solution build configuration, so I hope there will be a solution. :-( --Avonelle / comments
You are not alone. I just ran a build myself and am seeing this problem also. In my case, it is with Visual Studio 2019 not 2017, but yes otherwise the same error message. I really don't want to ha...
Other things I have tried: Updating to the latest version of SCA Updating to the latest version of SQL Compare Trying to import each view separately. None of these helped. Other information: I am using programmable objects, and I am using the Visual Studio version of SCA. I tried opening the project in SSMS, but it is showing many more pending changes than what the project (correctly) shows in VS2019. I'm stumped. I guess I will need to submit a bug report. :-( / comments
Other things I have tried:Updating to the latest version of SCAUpdating to the latest version of SQL CompareTrying to import each view separately.None of these helped.Other information:I am using p...
I am also experiencing this same issue with two views that need to be altered. I thought perhaps I could temporarily drop the views, import and generate script, and then recreate them, but that also did not work. I also made sure I was updated to the latest version of SQL Change Automation, but the problem persists. What can be done? / comments
I am also experiencing this same issue with two views that need to be altered.I thought perhaps I could temporarily drop the views, import and generate script, and then recreate them, but that also...
greg_burns wrote:
Apparently this is only works with Vault 6.0, not 6.1. The dlls are version 6.0.0.477, not 6.0.1.598.
Hmmm...I'm running Vault 6.0.0.477 standard, but I'm getting that "The Server edition is correct, but the version is wrong" error too. / comments
greg_burns wrote:
Apparently this is only works with Vault 6.0, not 6.1. The dlls are version 6.0.0.477, not 6.0.1.598.
Hmmm...I'm running Vault 6.0.0.477 standard, but I'm getting that "The ...
Thank you so much for posting this work around. I mistakenly upgraded Vault also, thinking it would be no big deal. Definitely a big oops on my part, but so far at least, this solution is getting me by. Hopefully a supported solution will be available soon. / comments
Thank you so much for posting this work around. I mistakenly upgraded Vault also, thinking it would be no big deal. Definitely a big oops on my part, but so far at least, this solution is getting m...