I'm searching for a tool window for hours and I cannot find it. (see http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-29-92-metablogapi/3386.Screenshot1_5F00_FullWindow_5F00_thumb_5F00_3CF6D767.png)
I found it in the Visual Studio 2015 Preview (I just installed), but I am 100% sure that I also had it in Visual Studio 2013 before. However, I cannot find it any more...
If you want to see CPU Usage, Memory Usage etc. you can go to the Performance and Diagnostics hub by going to Debug> Performance and Diagnostics or by pressing Alt + F2. I'm not sure it's identical to the window in the screenshot you posted, but it should give you the same information.
This blog post might help: http://blogs.msdn.com/b/visualstudioalm/archive/2013/07/12/performance-and-diagnostics-hub-in-visual-studio-2013.aspx
Diagnostic Tools while debugging are new in Visual Studio 2015. While there are similar tools in the VS2013 Performance and Diagnostics tool window, the project support between those tools and the tools that run while debugging in VS2015 can vary. For more information on the performance and diagnostic tools in VS2015, check out this blog post from one of my team members (I work at MSFT, and contributed to the tools you're referring to): http://blogs.msdn.com/b/visualstudioalm/archive/2015/07/20/performance-and-diagnostic-tools-in-visual-studio-2015.aspx
Visual Studio 2013 (CTRL+ALT+F2 )
Debug -> Show Diagnostic Tools
Visual Studio 2015 (ALT+F2 )
Debug -> Start Diagnostic Tools Without Debugging...
Related
I am unable to view memory usage in Visual Studio 2022 Community edition.
According to the Microsoft docs, there should be a memory usage option in the diagnostic tools.
However, my installation does not appear to have this option.
I've tried checking out the Settings for Diagnostic Tools and also reading every setting in Tools > Options > Debugging > General.
I've also run the VS installer with the profiling tools option checked.
How can I view memory usage in Visual Studio 2022 Community?
I'm running Visual Studio Community 2017 and none of the system library documentation summaries show in IntelliSense. I can't find an option to turn it on. Did I just miss in installing it or is there some way to turn this feature on?
While all the other versions and editions of Visual Studio I use on different machines bring up the Diagnostics Tools windows when I launch any of my projects in the Visual Studio debugger by pressing F5, the Visual Studio 2013 Professional edition installation I have doesn't.
It does have the diagnostic tools, though.
How do I get it to start the debug session with diagnostics and to display the diagnostics windows as well automatically upon starting a debugging session?
In VS2015, it has the option "Enable Diagnostic Tools while debugging" under TOOLS->Options->Debugging->General.
But it doesn't have this feature in VS2013. It has the function Performance and Diagnostics hub under Debug menu.
It was the new feature in VS2015:
https://blogs.msdn.microsoft.com/visualstudioalm/2015/07/20/performance-and-diagnostic-tools-in-visual-studio-2015/
When debugging a C# application in Visual Studio 2015, I am very often getting this message when hovering the mouse over a variable:
After this it freezes and restart, making it impossible to debug.
Anyone have any clue?
Like that thread shared by duDE, please disable the option "Enable property Evaluation and other implicit function calls" under Tools->Options->Debugging->General.
It seems that checking this option:
Tools -> Options -> Debugging -> General: "Use Managed Compatibility Mode".
avoids Visual Studio 2015 from crashing but disables Edit and Continue... which is no good.
So, I am still looking for a better answer.
Sources:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/8653d0d1-c7ed-4194-8fdc-f183d4ff4ec2/problems-with-debugging-in-vs-2015-when-execution-is-in-a-thread?forum=vsdebug
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/f3e0c708-0cb4-4e15-9f80-8e713870ebcd/debugging-cant-hover-over-variables-to-see-their-values?forum=visualstudiogeneral
Datatips (mouse hover over variables in debug mode) not working in Visual Studio 2012 / Win 7 64bit
Visual Studio 2015 Debugging: Can't expand local variables?
https://blogs.msdn.microsoft.com/visualstudioalm/2013/10/16/switching-to-managed-compatibility-mode-in-visual-studio-2013/
Quoting the last one:
In Visual Studio 2012, we introduced a new managed debug engine that provides us the ability to more rapidly add new features compared to the older implementation. This can be seen by the number of features introduced in Visual Studio 2013 after only a single year including Managed Return Values, .NET 64-bit Edit and Continue, Async Callstacks Enhancements, and Improved Tasks Window to name a few. Unfortunately, there are still a couple scenarios that are not supported yet with the new debug engine, so in these cases you will have to switch back to the legacy engine.
...so it seems that this is not new.
This issue should be fixed in Visual Studio "15" Preview 5 (available here. For Visual Studio 2015 Update 3 there are, unfortunately, no known workarounds other than those already mentioned.
I installed Visual Studio 2013 Release Candidate and after opening a project I noticed CodeLens information is not showing up.
In the preview versions you had to turn this on in the options menu, but I can't seem to find this option anymore.
Why doesn't this work?
You need Visual Studio 2013 Ultimate with Team Foundation Server 2013.
To use this feature you will need Visual Studio 2013 Preview and Team
Foundation Server 2013 Preview as some information comes from TFS.
and:
Here's what you’ll need:
Visual Studio Ultimate 2013 to find references
Team Foundation Server 2013 to find changesets, code review requests,
and different kinds of work items
Source
This article will tell you the same.
You can download Team Foundation Server here.
The option is hidden in
Tools -> Options -> Text Editor -> All Languages -> Code Information Indicators
The only one that appears to work for us is the references, even though all options are enabled.
Update: My missing options were answered here...
VS 2013 CodeLens
Hope this helps.