If you are working with a console application, by default the console output will appear in Visual Studio Code’s Debug Console window. Attach Debugging. The C# debugger supports attaching to processes. To do this, switch to the Debug tab, and open the configuration drop down and select “.NET Core Attach”.
Honourablesandeep 8-Aug-17 7:11 8-Aug-17 7:11 Hello Mr Pankaj Chamria I have some projects in vs 2010 vb.net but but suddenly f11 step into stopped working simply debugger is not stopping at any break points in any module tried various Microsoft forums plus stack overflow website guidance but in vain tried cleaning cache, temp files, deleting bin and or obj folders from Windows explorer, deleting.suo files, setting general debugging options but couldn't help me out so do you have any guidance regards to this if any please help thanks.
I need to debug an application that is started from a one-click install. (VS 2010, Excel VSTO with Office 7). Based on login credentials supplied to the one-click installer application, the user should see one of two splash pages. This all works fine on my machine, but when deployed, changing from the default to the second splash page results in an error. For the life of me, I can't figure out how to debug the process from within VS2010. I can attach to the login before entering the credentials, but I can't attach to Excel because it isn't launched until I click the OK button.
So, is there some way to have Excel, or rather, my code call the debugger as it is instantiated so I can figure out why my image resource isn't available in the deployed application? You could attach to Excel if it was running long enough but seriously I doubt the error is there.
You could attach to running applications/processes and if symbols are available (debug build) you can really debug, but the application has to live long enough for you to select it for attaching. I think, from what you are saying, that what you need is proper exception and error logging, anything like Log4Net or NLog which stores everything (stack trace, exception details.) at every exception, so you would clearly identify what the real issue is. To force a breakpoint from code use: if (System.Diagnostics.Debugger.IsAttached) System.Diagnostics.Debugger.Break; Sometimes the application has to be started outside the Visual Studio. Then I use this code to attach the debugger later: using System.Diagnostics.
![Debugger Debugger](/uploads/1/2/5/4/125463644/209445029.png)
Process procName = Process.GetProcessesByName('devenv'); // check if VS currently running if(procName.Length 0) MessageBox.Show('Wait for debugger attach'); if (System.Diagnostics.Debugger.IsAttached) System.Diagnostics.Debugger.Break; // force a breakpoint.