You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After installing this extension, I noticed between debug sessions, that VS would rebuild even if I didn't change any source code. (might not notice if you're a C# guy, but believe me, us C++ guys get hammered by this if we have a common header file opened in VS, it can lead to a 10 minute build penalty). Anyhow, turned out to be this extension was the root cause.
Here's the fix to the ShouldSaveDocument() function that solves the issue
: internal bool ShouldSaveDocument(Window window, OptionPageGrid optionsPage) { if (!window.Document.Name.Contains("*")) return false; ....// all the original code can stay }
VS adds a * to the modified and unsaved buffers. Now it only saves modified files and is so much more useful for me. I've tested this change and it resolved my issue. Hopefully you'll include the fix in the next update.
The text was updated successfully, but these errors were encountered:
After installing this extension, I noticed between debug sessions, that VS would rebuild even if I didn't change any source code. (might not notice if you're a C# guy, but believe me, us C++ guys get hammered by this if we have a common header file opened in VS, it can lead to a 10 minute build penalty). Anyhow, turned out to be this extension was the root cause.
Here's the fix to the ShouldSaveDocument() function that solves the issue
:
internal bool ShouldSaveDocument(Window window, OptionPageGrid optionsPage) { if (!window.Document.Name.Contains("*")) return false; ....// all the original code can stay }
VS adds a * to the modified and unsaved buffers. Now it only saves modified files and is so much more useful for me. I've tested this change and it resolved my issue. Hopefully you'll include the fix in the next update.
The text was updated successfully, but these errors were encountered: