- Home /
- Visual Studio /
This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more
Report an issue
in Visual Studio Installer or Visual Studio
This allows diagnostic information about the program to be included in your report
1. Installer or Visual Studio
2. Report a Problem
3. Type and Submit
Available on Visual Studio 2017, Installer, and newer releases
Would you like to know more?
"Save all" tries to save closed .sql query tabs.
1) Load up your solution.
2) Open query executor from data connections and write something.
3) Change some of the files in your project.
4) Click 'Save All'. This will try to save .sql file since it's still opened in your tabs.
5) Cancel saving operation and close the .sql tab.
6) Click 'Save All' again. It'll prompt you to save .sql file but there's no opened .sql query in my tabs anymore.
It only must save my opened tabs. I do not care an sql query is saved or not since it is closed and I'm not interested anymore. Caching problem?
I am also encountering this issue. Opened a sql query to execute a select against a local database, closed the tab, told VS to not save changes. Attempted to Save All later on and it still requests to save the closed .sql tab.
Encountered the same issue on latest Visual Studio 2017 15.3.1
Really annoying, since it will lead to a non-working "Save All" button.
Still occurs on 15.3.3
You are not able to check in some changes, if there was a .sql file opened and closed. VS always asks for saving changes of a non-existent tab.
If you choose to save the "closed" sql windows to a file and open that file later, you will see that it contains the SQL text that the window contained before you clicked the "X" to close it. It appears as if the "X" hides the window, but keeps open the buffer containing the unsaved text. The side effect of the buffer staying open without a window is all of these questions about closing it.
Absolutely incredible that release after release Visual Studio (Now in 15.4.0) continue to have this bug (probably simple to solve, since the user jotting posted his vsix plugin to mitigate) . It is really annoying for who like me keep sql scripts into a TFS account and is used to edit and launch them directly from VS.
There 202 people following and 38 upvote.
I'd like to have it fixed for the next release, we usually not play with Visual Studio, we work with it.
Under Investigation from August...
For a similar issue, if not solved in days, I'll get fired.a
Not fixed in 5.4.1 either... and in that release you have been fixing things with no votes. What's the go microsoft?
Best Solution
Thanks! So it seems the file is never discarded, even though the "Save changes" popup was answered with "No".
Fun fact: if you create a new query from the SQL Explorer window and immediately close it (which won't trigger a "Save changes" popup, since it's an empty file), you still get a new SQLQueryX.sql file. This shouldn't be hard to fix, I would guess.
Translated from Bing:
This bug has been going on for a year, and the current version 15.4.2 has not been fixed~ Is it so difficult to fix?
@Blair Wang-MSFT I'm on 15.4.5 and still experiencing the issue.
15.5.0 is out and fixes that issue in my case.
How can I force VS to refresh the notifications pane? 15.5.0 doesn't show up.
Does this mean I need to download the full installer to get 15.5? It does not show up in notifications.
I ran the installer that I had on my PC and it updated itself and then downloaded the new version of Visual Studio after that.
As of 7/25/2018, VS 2018 still has this incredibly annoying bug.
Are your sure? This problem has been fixed for me for a couple of months now -- since 15.5.0
Make sure you're using the latest version, at this time it's Visual Studio 2017 version 15.7.5
(if Visual Studio doesn't show you any update prompts, try running the Visual Studio Installer)
265 People are following this
