Comments
Sort by recent activity
Hello @Kendra_Little, thanks for your quick response! Yes it is a YAML rather than classic. Ahh so the "<pipeline>\s" is not the proper place for the nupkg – I see that now. I also found that all of the build nupkg files are in "<pipeline>\Database Build Artifact" anyway with their respective build names, so rather than adding a download task, I've just told it to get the current nupkg from that folder using the build number and it seems to have worked. And for safety's sake/to be thorough, I'd better sort the other pipelines lest they start having the same problem... Thanks for your help! Kris / comments
Hello @Kendra_Little, thanks for your quick response!Yes it is a YAML rather than classic.Ahh so the "<pipeline>\s" is not the proper place for the nupkg – I see that now. I also found that all of ...
I get the same issue. I updated my SSMS but it still wouldn't open, so I reinstalled SQL Source Control and it now works, but it's still asking me to update. Strangely it says I'm on 7.1.30 and need to update to the 7.1.30, which it has done that for a few updates now. / comments
I get the same issue. I updated my SSMS but it still wouldn't open, so I reinstalled SQL Source Control and it now works, but it's still asking me to update. Strangely it says I'm on 7.1.30 and nee...