In Visual Studio 2015, the build notification program used to pop up a Window. Since I've upgraded to VS 2017, it now produces a toast notification, which is easy to miss, and once it has faded (about 5 seconds), there is no way to get it back. The notification seems to be the only place where the build reconciliation option is available.
Is there either a way to reconcile other than from the notification, or is there a way to configure the notification to be a window rather than toast?
Related
Unable to sign into TFS online using visual studio professional 2017 v15.2 (26430.14) - Visual Studio locks up few seconds after login dialog appears...
Seems sign-in dlg is displayed as VS attempts to connect to TFS online; but no matter what you do you get locked up 3 secs later.. No matter what... end result is me killing the process and left unable to access any project.
THE ONLY WAY OUT I did figure out that if you cancel(esc key) the dlg closes before it hangs. you can THEN connect to TFS via team/menus. life saver.
does anyone know why this happens or how to correct..? seems intermittent but sometimes lasts for days.. meaning, I have to do this on every startup; but then magically the problem goes away. An associate of mine also sees this problem.
It looks like this issue is resolved with the latest VS2017 update (15.0.26430.16).
I'm not sure what version you are running, but try updating as it worked for me.
I'm used to seeing an update option in Help About. How do you update the Visual Studio 2017 IDE to the latest version?
While in the Visual Studio 2017 IDE, you'll see a yellow flag in the title bar that indicates that at least one notification is waiting:
You can single-click that flag icon to view the notifications. If you see an update, you can click the link. That takes you to the Extensions and Updates window.
But to get to updates when you might have dismissed notifications or when you don't see the yellow-flag icon, you can get to that window directly. To do that, go to Tools | Extensions and Updates. On the left pane select Updates. You'll see a list of available updates. To install one, click the Update button. In the image below, Visual Studio Update 15.1 (26403.7) is available and its Update button appears on the right edge of the selected item.
I recently upgraded from Visual Studio 2013 Community to Visual Studio 2015 Community.
I've heavily relied on the "CPU Usage" Tool that can be found by doing the following:
Click "Debug"
Click "Start Diagnostic Tools without Debugging"
Click "CPU Usage" Check box
Click "Start" button
When the program is complete, it is supposed to show you the functions and the time spent in each. What I get instead is just the name of my executable that I can keep expanding instead of seeing the function names -- It doesn't know the names of the functions.
This worked fine on Visual Studio 2013... I would be able to see the function names and everything worked. I tried creating a new "test" solution/project to see whether this works and I get the same results: No function names.
Does this work for anybody? I also installed VS2015 on a fresh development box and still have no results. This seems like Microsoft shipped with a Visual Studio bug.
Note: I'm writing a C++ console application. I've tried this on debug and release builds and ensured that I'm building with debug information.
It's in the Visual Studio 2015 Update 1 release notes, so I suspect it was broken in the initial release:
Profile your CPU Usage while debugging
Now, you can get a detailed per-function profile of your CPU Usage while you are debugging. You can turn CPU Profiling on and off while debugging and view the results when you are in a break state, which allows you to view a per-function breakdown of CPU Usage of code that executed between breakpoints and during steps. (To use this functionality, open the Diagnostic Tools window (Debug -> Diagnostic Tools), switch to the CPU tab, and then click the "CPU Profiling" button.)
I have also noticed this, but if you use that little search box (top right corner of the results area) and try typing in either the name of the function you're looking for or part of the name and it will expand everything (there's usually a lot to expand) and highlight the function you're looking for. Its the only way I've been able to profile specific functions.
I have created a multi device hybrid project in Visual Studio 2013.
I am having a few major issues:
1) Changes to my scripts do not appear unless I completely rebuild the application when I am using Ripple to view the project.
2) Pressing F12 in the Chrome ripple window causes Visual Studio to stop running the application. This seems very strange. It's like if I were to quit debugging on a normal webapp.
Output shows The program '[1] http://localhost:4400/index.html?enableripple=cordova-3.0.0-NexusGalaxy: WebKit' has exited with code -1 (0xffffffff).
Has anyone had these problems or know what might be causing them?
Both of the behaviors you describe are expected. Ripple is not automatically refreshed when you save your changes so you will need to rebuild and deploy for it to pick up the updates. Since only one process can use the webkit debugging at once, the VS debugging session gets disconnected when you use the debugging tools in Chrome.
I am using Visual Studio Premium 2013 Update 2 on a freshly installed (fast) machine with Windows 8.1 Update. Everything is running smoothly, only one thing bugs me:
Problem
When I debug a native C++ project (debug build) by going from line to line with F10 ("step over") it takes 1-2 seconds to go to the next line when I press the F10 key.
What I tried
I looked at several other questions related to slow debugging and made sure that neither of the following is not the reason in my case:
Everything is local (app and all data), no network shares involved
Disabling the Microsoft symbol server did not help
I only have a single breakpoint
Using the menu/toolbar instead of the keyboard does not make any difference
In the default configuration "edit and continue" is enabled, but apparently not for native code:
When I disabled "edit and continue" completely, F10 stepping became much faster (0.5-1 s). The speed is tolerable now. I had to restart Visual Studio after I changed the configuration to this: