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?
Related
I'm trying to debug a Web Forms application written in VB.Net and Visual Studio (2017) keeps hanging as soon as I try to move through a breakpoint.
The Locals window shows "Busy..." and is never populated with any variables (see image).
Debugging an MVC application works.
I've tried updating VS to the latest version, running in Safe Mode, removing the bin and obj directories, and rebooting; all to no avail.
I've also pulled the code into a new local repository from the current working version in TFS and it crashes in the same place.
Am I missing something obvious or is a re-install the next step?
I am developing an ASP.NET MVC4 application in Visual Studio 2015. For debugging I run it on the IIS server (v7) installed on my development machine.
Recently, when I change something in the source code and go to debug it Visual Studio says 'Trying to Contact the Web Server' then times out. When this happens the start menu (I am running Windows 7) becomes unresponsive (it opens but you cannot select an item or type anything in). I ultimately have to restart my machine, which is very time consuming.
I have tried running iisreset from the command prompt, but it doesn't fix the issue. It takes a long time to restart IIS.
Does anyone have any suggestions as to what may be causing this?
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.