Comments
Sort by recent activity
StephanieHerr said:
Hi. This is now generarlly availble on the marketplace - https://marketplace.visualstudio.com/search?term=redgate&target=VS&category=All categories&vsVersion=vs2022&sortBy=Relevance and also in our Redgate Deploy installer - https://www.red-gate.com/products/redgate-deploy. Thank you!
Thanks Stephanie, have had it back for a few days now. I still think this was a dastardly plot to make us try the SSMS version! [image] / comments
StephanieHerr said:
Hi. This is now generarlly availble on the marketplace - https://marketplace.visualstudio.com/search?term=redgate&target=VS&category=All categories&vsVersion=...
StephanieHerr said:
We are actively working on this and plan to release at the beginning of Jan. There were a lot of little changes with this release that required more work than expected. There are also changes that we need to make so we don’t break the previous versions of Visual Studio. We’ll post again once it’s available. Thanks for bearing with us.
Thank you Stephanie. This is all (most of us) wanted... an update! Thanks again! / comments
StephanieHerr said:
We are actively working on this and plan to release at the beginning of Jan. There were a lot of little changes with this release that required more work than expected. ...
EricLamontagne said:
Guys come on! Yes it will be nice to have support for 2022, but how do you know they are dragging their feet? It can be much more complex than you think it is. Anyway, 2022 is still a month away :upside down:
Complexity has nothing to do with it. Communication is the issue. If 2022 caused massive breaking changes, fine, communicate that. If they have to redesign the entire process because of .NET 6, fine, communicate that. Saying "the team is working on it" is not communication, it is stonewalling. I can except a delay with meaningful communication, and I don't need all the nitty gritty details, just something more than "we're working on it". I see this A LOT with other vendors, usually smaller ones. Redgate usually does a really good job at communicating on issues, but they are strangely silent on this one, which is concerning. / comments
EricLamontagne said:
Guys come on! Yes it will be nice to have support for 2022, but how do you know they are dragging their feet? It can be much more complex than you think it is.Anyway, 202...
Hello, Can we AT LEAST get a timetable? You guys are really dragging your feet on this one. I'm used to this from other third party providers, but I am not used to this from Redgate. / comments
Hello,Can we AT LEAST get a timetable? You guys are really dragging your feet on this one. I'm used to this from other third party providers, but I am not used to this from Redgate.
Stephanie, OK, VS 2022 is officially released. You should have been ready to release. I know it's been only a week, but of all my third party tools, you guys are the only one not available/ready. No extensions for Redgate in VS 2022 currently exist. Particularly SQL Change Automation. Thanks, Greg / comments
Stephanie,OK, VS 2022 is officially released. You should have been ready to release. I know it's been only a week, but of all my third party tools, you guys are the only one not available/ready. ...
Thank you Monday... your response helped me do a little Joe Friday and was able to figure it out! [image] For some reason the ODBC SQL tools (SQL Cmd Line Utils) didn't install on the client. Once I manually installed them, everything was good. Thanks Again! / comments
Thank you Monday... your response helped me do a little Joe Friday and was able to figure it out! For some reason the ODBC SQL tools (SQL Cmd Line Utils) didn't install on the client. Once I man...
Thanks Sergio, you are correct. That machine did have some issues in PowerShell that needed to be cleaned up. That seems to be happening more and more these days (that's a Microsoft knock, not a Red-Gate knock!) [image] / comments
Thanks Sergio, you are correct. That machine did have some issues in PowerShell that needed to be cleaned up. That seems to be happening more and more these days (that's a Microsoft knock, not a ...
I can confirm that as of v4.0.19255.10541 the project settings are now visible in Visual Studio 2019. Thanks Guys! / comments
I can confirm that as of v4.0.19255.10541 the project settings are now visible in Visual Studio 2019. Thanks Guys!
Just to keep this thread updated. The release of SQL Change Automation 4.0 has not resolved the issue. / comments
Just to keep this thread updated. The release of SQL Change Automation 4.0 has not resolved the issue.
Russell, I am doing more testing, but it's taking time. (I forgot) we have some automation scripts that install some extensions for Visual Studio after installing VS. I'm removing these one at a time to see if any of them are interfering. The problem I have is that these same extensions install on VS 2017, and I don't have the issue. Also, when you open the properties page, it "looks" like the properties try to load (it flashes), and then get blocked. I just don't get what that could be. Thanks, Greg / comments
Russell,I am doing more testing, but it's taking time. (I forgot) we have some automation scripts that install some extensions for Visual Studio after installing VS. I'm removing these one at a t...