visual-studio-debugging

I am struggling to better grasp the rationale of exception and error handling in TPL (and with some more luck in .NET 4.5 async/await tasks) The slightly modified from my earlier question "How to better understand the code/statements from "Async - Handling multiple Exceptions" article?" C# console app code running 2 detached inner nested attached (dependent) child (Update: sorry, started one question but ended by another!) tasks: class Program { static void Main(string[] args) { Tst(); Console.ReadLine(); } async static Task Tst() { try { await Task.Factory.StartNew (() => { Task.Factory

My goal is to debug Asp.net MVC 5.2.3 source code. I created Asp.net MVC application in Visual Studio 2013 and updated all NuGet packages. Set up VS2013 as described in https://referencesource.microsoft.com/setup.html Added http://referencesource.microsoft.com/symbols , https://nuget.smbsrc.net , http://srv.symbolsource.org/pdb/Public , http://srv.symbolsource.org/pdb/MyGet , http://msdl.microsoft.com/download/symbols https://nuget.smbsrc.net to symbols But when I'm trying to "Step Into" View method of Controller I see "Controller.cs not found". When I'm trying to navigate to stack trace I see

Is there any way to change the default behavior of Visual Studio's debugger such that when hovering over a null-terminated, dynamically allocated character array (C++), it will display the full content of the string, rather than the first character only? I should mention that I am using Visual Studio 2010. If there is a way to achieve this in VS2012 only though, I would be interested to know that as well! There's a useful link for visual studio, C++ Debugger Tips : To interpret a pointer expression as a string, you can use ‘,s’ for an simple null-terminated string, ‘,s8‘ for a UTF-8 string, or

I recently started having problems with breakpoints in Visual Studio 2010. When I set a breakpoint and then start debugging, another breakpoint appears on some other line nearby. The screenshots below shows the editor after I set a breakpoint, as well as the breakpoints window: As soon as I start debugging, the breakpoint duplicates, as seen in the following screenshots: Why is this happening and how can I stop it? David It looks like there is a child breakpoint set up, as described in the following MSDN articles: http://msdn.microsoft.com/en-us/library/b98cwcyw.aspx (Link dead, see Child

Tools: Windows 7, Visual Studio 2010 and 2012, IE 9, ASP.NET 4.0, MVC4 Until a couple of days ago I had been able to debug by using the Script Documents section in the Solution Explorer. Now, the Scripts Documents section does not appear when Start Debugging (F5). I do have IE set as the default browser. Using "debugger;" has no effect. Configuration is set to "Active (Debug)." Silverlight debugging is off. I have 'repaired' the Visual Studio 2010 inatallation. I have no idea how to correct this frustrating situation. What have I done to displease the VS gods? Thanks for any advice! Arnold

I'm using VS2010 Beta 2 to debug some multi-threaded code. Love parallel stacks, etc. I have a question, though: I have a breakpoint set in a method that may be called by multiple threads. Once I hit the breakpoint, I really want to keep the focus on the thread that triggered the that breakpoint. However, when I hit "step", VS often switches to another thread (say I'm stopped on thread 1, but in the meanwhile, thread 2 hits my breakpoint). I know that I can manually freeze threads in the thread window. Is there a way to do it automatically -- basically, once I hit a breakpoint, freeze all

Configuration: Windows 7, 64 bit Microsoft Visual Studio Professional 2012 RC Version 11.0.50522.1 RCREL Running VS in administrator mode The VS solution contains a web application, with target: .NET Framework 4. When I press F5, the solution builds... and nothing else happens. Happens with both IIS or the VS Dev Server. Happens with Platform Target of "Any CPU" or "x86" If instead, I use the Debug / Attach to Process... menu, after a few seconds, I get: "Debugger is Busy" - Debugger is performing a remote operation that is taking longer than expected. This dialog stay until I click "Terminate

In short: Console.WriteLine was working ok in VS 2015 but it is not working anymore in VS 2017. In detail: I have some VB code using Console.Write that outputs ok to Output Window in VS 2015, even when configured as Release ( to contrast with Debug ) launched with Start Debugging ( in contrast with Start Without Debugging ). Today I upgraded to VS 2017 ( Community version ), but the Console.Write is not working anymore in the same conditions as VS 2015. Maybe I made some config in VS 2015 in the past, but I do not recall. Can someone help me how to make Console.Write output to Output Window in