Comments
Sort by recent activity
Hi @DanC, I still do not think that you're completely understanding the issue. My pipelines are using the SCA Build Task as is described in your previous post above--we have been for years. The issue remains this:
The SCA project is part of the VS solution.
The VS Build task started failing with the release of SCA 4.4.22194.30982
The VS Build task does not allow for exclusion of the SCA project from the solution--instead would require me to rework/redefine the VS configurations for approximately 50 solutions, then updating the 150 pipelines (50 each of WIP, QA, and Prod).
The fact that Redgate chooses to remove the support for VS Build is totally fine with me--but it is NOT fine that this release of SCA has broken 150 pipelines.
We can agree to disagree on this topic--I just won't do it on a public forum any longer. Instead, will work through our support agreement with Redgate so that I can talk directly to someone to perhaps better explain the issue. Thanks much for your responses, Pam / comments
Hi @DanC,I still do not think that you're completely understanding the issue. My pipelines are using the SCA Build Task as is described in your previous post above--we have been for years.The issue...
Hi DanC, The link to the documentation refers to AzureDevOps -- not Azure DevOPS Server (formally known as TFS). I believe that all of us having this issue are using on-prem build machines. I read that Redgate will not longer support the MS Build task. However, since this step is a required step for building other projects in my solution, I'm not at liberty to simply exclude this task from my pipeline. I also know that there is a very painful workaround that would require creating VS configurations to specifically exclude building the SCA project during the MS Build task. However, the impact of making this change to many, many, many solutions is untenable. I would respectfully request that Redgate consider the impact of this change on its users and perhaps, with the end of your support of the MS Build task, at least provide code that does not otherwise break pipelines. Thanks, Pam / comments
Hi DanC,The link to the documentation refers to AzureDevOps -- not Azure DevOPS Server (formally known as TFS). I believe that all of us having this issue are using on-prem build machines.I read th...
Hi DanC, I hate to belabor the point, but my original post describes the pipeline issues I am having. And, per posts from other users, they also are experiencing the same issue. "...we have a specific step for SCA (that is NOT failing). However, when the Visual Studio Build "Build solution" step is executed, the SCA build fails because te DBClean task cannot locate a specific version of Newtonsoft.Json..." So, the task that is failing is the Microsoft "Build solution" task. It worked prior to the latest update of Redgate tools and now is failing. I do not have the ability to control how the "Build solution" task interfaces with Redgate tools. Would it be possible for Redgate to weigh in on why the "Build solution" task is failing since this is the error that was introduced with the most recent update of SCA? Best regards, Pam / comments
Hi DanC,I hate to belabor the point, but my original post describes the pipeline issues I am having. And, per posts from other users, they also are experiencing the same issue."...we have a specifi...
Hi DanC, Sorry...my original post must have been misleading. We are using on-prem Azure Dev Ops server (or what used to be called TFS). We have not used ReadyRoll for quite some time (years?). The only Redgate component that is accessed from my pipeline is "Redgate SQL Change Automation Build", with the version setting of "Latest". According to the VS Marketplace, this plugin has not be updated since 5/11/2022, so I do not perceive that the version of SCA Build is the issue. Where would you expect that I might see the "ReadyRoll" reference that you're referring to above? Thanks, Pam / comments
Hi DanC,Sorry...my original post must have been misleading. We are using on-prem Azure Dev Ops server (or what used to be called TFS). We have not used ReadyRoll for quite some time (years?).The on...
Hi clinke, The only way I could get a previous version working on my build server was:
I uninstalled SQL Change Automation completely from the server
Since we have multiple versions of VS on the server, I confirmed that the extension is not still being referenced in any of the versions of VS. (If it is, remove the extension from VS)
I Installed the specific version of SCA that most recently worked in a successful build. Thanks to clopez above, I used the link that he added to his post (minus the exe) and found the Redgate downloads directory that allowed me to locate the version I was looking for (https://download.red-gate.com/checkforupdates/SQLChangeAutomation)
Installed this version. When prompted, take one of the options that installed the component into VS. After installation, all versions of VS were using the specific version that I wanted.
Other things to note:
You'll likely want to turn off the "Automatic-update" option in VS for this component, or it will be overwritten the next time that Redgate auto-updater runs
The uninstall / reinstall of SCA required reboots of the build server
Hope this helps, Pam / comments
Hi clinke,The only way I could get a previous version working on my build server was:
I uninstalled SQL Change Automation completely from the server
Since we have multiple versions of VS on the ser...
Dan, Thanks for your response. However, I've attempted what you suggest, without success. Just to give context, I am using SQL Change Automation from within Visual Studio. I manually added the following line to my sqlprl file: <UseCreateOrAlterForRerunnableScripts>True</UseCreateOrAlterForRerunnableScripts> I manually changed the "SyncOptionIgnoreWhiteSpace" option to "True". I then added a space to a script (from SSMS), then "refreshed" from Visual studio. The script was not modified, so I made a substantive change to the script, and then "refreshed". The script was now altered (a blank line was added), but the new "CREATE or ALTER" text was not added to the script. Can you provide any additional options for getting this to work? I have 8 existing projects with SQL Change Automation included which need this option (due to replication of views). Even if the steps you suggested worked, performing the steps on each programmable object will take an enormous amount of time. Are there any shortcuts other than what you suggest above? As I brought this feature request to my Red-Gate sales/tech contacts, I shared that the inability to deploy replicated views was a blocking issue that prevented me from deploying SCA projects without having replication removed during deployment. I was thrilled when I heard that the feature was added to SCA, but I had envisioned a more user-friendly method of applying the change to my existing projects. Thanks, Pam / comments
Dan,Thanks for your response. However, I've attempted what you suggest, without success. Just to give context, I am using SQL Change Automation from within Visual Studio.I manually added the follow...