Open Visual Studio 2013 in Windows 8.1
Create New project -> Visual C++ -> Windows Store -> Blank app (XAML)
Run (in Debug mode)
Press Close button ([X] button in the top right corner on the screen)
Behavior:
Visual Studio Environment waits for about 15 seconds and then it prints messages in the Debug output console:
Thread 0x123c terminated with code 0 (0x0)
Thread 0x223 terminated with code 0 (0x0)
...
You have to wait for about 15 seconds to see next message, and debugging does not stop until you finish it by pressing "stop debugging" in the Visual Studio. Then Visual Studio prints other 8-10 messages in Debug output, prints
Program "[4388] App1.exe" terminated with code 0 (0x0).
and stops debugging.
Expected behavior:
Normal program finishing in 1-2 seconds without tons of thread terminations.
Any help is appreciated.
Thanks for the attention.
Related
Tried shutting down my laptop, a windows 7 os on Sunday afternoon. Then I got a notification telling me that a program was still running, forced the system to shut down because I was in a rush. Then on Monday morning, I powered up my system and tried opening visual studio code editor by clicking on the shortcut on the desktop. When I click, the loading circle spins for some seconds then stops. Nothing else happens. It doesn't open. Did this several times. I have uninstalled and installed visual studio code 4 times,but it's still the same thing. Even after downloading and installing its meant to open / run automatically, but instead it doesn't. Please what can I do? This is really frustrating.
When I run an application in Debug mode in Visual Studio and close it, the application does not get killed as expected. The window closes successfully but the process keeps on running in the background.
As a result, when I try to launch the application again, Visual Studio gives me an error stating that .dll is being used by another process.
What could be the issue?
I'm using Visual Studio 2015 to debug a website running on a .NET framework. When setting break points in one of my .aspx.vb files it gives me an error saying:
"The break point will not be hit. No symbols have been loaded for this document."
Now I have solved how to fix this error by going to Debug -> Attach to Process then attaching it to the process of my IIS.
The issue is I have to do this every time I stop and restart debug mode. Is there anyway to get this process to automatically attach when I begin debugging?
The ReAttach extension gives you an easy way to ReAttaching your prior debug targets.
I have created a COM add-in for Excel.
I know that I can enter debug points into my code and then choose to "play" my code from Visual Studio. When a debug point is hit, execution stops and I enter debug mode.
But is it possible to create debug points that cause execution to stop and debug mode to start when I am not running my code via "play" in visual studio but just opening an Excel file as normal?
You can attach the debugger after you run Excel manually outside of Visual Studio. See Attach to Running Processes with the Visual Studio Debugger and How to: Attach to a Running Process for more information.
I am compiling and running code at runtime. Can I stop this code midway through if I wish? Like the 'stop' feature in Visual Studio that stops the code if desired?
You can, if you attach the Visual Studio debugger to the running process.
Load the solution that produced the application into Visual Studio
Run your application outside of Visual Studio
Choose Debug -> Attach to process... from the Visual Studio menu
Select your application in the process list
Click Attach
You should now be able to use the normal debugging controls to pause execution of your application, step through code, etc.
Yes, it's called the task manager (find your process and kill it). Or if you're in a console window, just use Ctrl+C.