Activity overview
Latest activity by mmoore
I was having issues with servers and databases not connecting to Source Control. However, after installing an update, I was able to connect and then shutdown without SSMS restarting by itself. I am going to do more testing to make sure this is fixed. / comments
I was having issues with servers and databases not connecting to Source Control. However, after installing an update, I was able to connect and then shutdown without SSMS restarting by itself. I am...
The first fix they gave me about a week ago did not solve the problem, but it seems to aggravate it even more. I just downloaded the newest version now and will test it shortly. / comments
The first fix they gave me about a week ago did not solve the problem, but it seems to aggravate it even more. I just downloaded the newest version now and will test it shortly.
Adievo said:
is anyone trying to fix this?
I was told to update to the latest SQL Source Control version, which I am going to do later today to find out if this fixes the problem (7.7.17.19083).. What is funny though, when you do "Check for update" in Sql Source Control, it says there are no updates, and I am currently on (7.7.10.18663) / comments
Adievo said:
is anyone trying to fix this?
I was told to update to the latest SQL Source Control version, which I am going to do later today to find out if this fixes the problem (7.7.17.190...
so, is this a SSMS issue or a Red-Gate issue?
jembree said:
Add another one to the list here. Sean B's work around of closing connections before closing program seems to work. SeanB said:
I have been having this problem too for a few months. Today I upgraded from SSMS 19.3 to SSMS 20.1 (Windows 11 box). Although SSMS is supposed to import options and customisations, it definitely doesn't do them all - including toolbars. I like my toolbars to have my most used tools and not filled with stuff I don't want. So I modified the toolbars to the way I wanted, then exited out of SSMS. Unfortunately, SSMS automatically restarted (again) and the toolbars had all reverted (or, more specifically, nothing had been saved). After various fumbling about, I found a workaround how to stop this happening: Disconnect from all servers before exiting SSMS.
The object explorer should be empty. This will stop SSMS restarting, and also allow you to save changes to toolbars (and perhaps other things). (Note that it seems to be OK if you didn't actually open any databases, but if you have opened a database, then disconnecting from the server, before exiting SSMS, allows you to exit without restarting).
/ comments
so, is this a SSMS issue or a Red-Gate issue?
jembree said:
Add another one to the list here. Sean B's work around of closing connections before closing program seems to work. SeanB said:
...
This is happening to me as well, even on servers that have no linked database so source control. What sucks, is all the remembered tabs are closed as well. / comments
This is happening to me as well, even on servers that have no linked database so source control. What sucks, is all the remembered tabs are closed as well.
I just rebuilt from scratch, and these same assembles that are labeled as unable to be embedded are still embedded. This is causing a huge issue for us, as we cannot obfuscate our product now. If we include these in the obfuscation, our application will not run afterwards. The only means of me removing them is to remove them from the saproj file manually with notepad, but as soon as I open it with the app in the GUI, if I click save, they come back. / comments
I just rebuilt from scratch, and these same assembles that are labeled as unable to be embedded are still embedded. This is causing a huge issue for us, as we cannot obfuscate our product now. I...
Adding new assemblies to project adds a bunch of un-embedded assemblies
We added a few nuget assemblies to our .net project (Microsoft.Sharepoint.Client & Microsoft.Sharepoint.Client.Runtime & Telerik.WinControls.Scheduler. Now, when I obfuscate our project, it adds ...
These 3rd party apps are going to be the death of me..lol / comments
These 3rd party apps are going to be the death of me..lol
Actually, I found the issue. We are using Snag-It and by default, it is using Ctrl+Shift+D, which was preventing SSMS from allowing to intercept it. Once I changed that in Snag-It, Ctrl+Shift+D worked in SSMS. We can close this... FWIW, this happened when we first got Snag-It a few years ago, but I totally forgot about it....UGH.... / comments
Actually, I found the issue. We are using Snag-It and by default, it is using Ctrl+Shift+D, which was preventing SSMS from allowing to intercept it. Once I changed that in Snag-It, Ctrl+Shift+D w...