I am running visual studio 2017 community version 15.7.6.
I am running an asp.net web application in debug mode. When I hit the "Stop" button to stop the debugger, it continues to run the program. I have to close Visual Studio completely to get the program to close.
Things I have tried:
Tools -> Options -> Projects and Solutions -> Web Projects -> Stop debugger when browser window is closed is checked.
Enable Edit and Continue under in the .csproj is checked.
I have closed IIS Express in the System Tray.
Running my application using the Visual Studio 2013 debugger produces the correct behavior, so this issue is just with the VS 2017 debugger.
Nothing works in VS 2017 except closing visual studio completely.
Does anyone know what is going on?
Right-click the IIS Express icon in the Notification Area (aka System Tray), then, under "View Site", hover over your web application. In the fly-out menu, choose "Stop Site". That usually works for me.
As far as I know, Visual Studio just does this sometimes and there's not anything you can do about it. If it's happening consistently I would try reinstalling and/or reverting to older versions to see if the issue persists.
Related
My visual Studio 2017 community keeps freezing and i get the error message not responding when i deploy a Provided hosted add in to SharePoint. I can run all other types of projects that i have tried without any problems. I have a newly installed windows with just a few programs on it. I can run a console application to my SharePoint online without any problems. So i guess SharePoint isn't the problem.
What i have tried:
Reinstall windows
Reinstall Visual Studio
Reinstall ISS
Update Visual Studio
Update windows
Disable some debug options (Read online that might help)
And some minor things
I appreciate any help/tips i can get everything is helpful at this point.
i had same problem and i figure out its firefox problem, so when i uninstall firefox, problem solved for me,
may be it help you as well.
Same issue for me, you need to change the default browser from "Start Action" to "Internet Explorer" in the Add-in project properties pane.
I recently reinstalled visual studio 2015, and for some reason I can't start the debugger for an asp.net web application by pressing F5 as I used to do. Visual studio is trying to attach to my firefox.exe process ; at first it was complaining that the process was 64bits, and now I solved that it wants me to set a "start page" which I don't want to, and it doesn't start the web server in debug mode anyway. Which means I can't set breakpoints or catch exceptions in the debugger.
Turns out the problem was that ASP.NET was not checked in the project properties in the Web tab. This is needed to enable server-side debugging.
Instead, Silverlight was checked, which caused visual studio to try to attach to the browser. I never, ever, wrote anything related to silverlight, I have no idea why this was checked, as far as I know I didn't even open the properties page since I reinstalled visual studio.
There is an old similar question without answer so I've decided to ask if someone has a hint on this:
I've installed a new Windows 10 Laptop with Visual Studio Enterprise 2015.
After setting all up, I've checked out one of my solution, that is working perfectly on Windows 7 and VS 2013 and I have the problem indicated on the subject.
I start the application, I can debug it or stop the debugger without problems, but if I close the application the application closes but the debugger remains active.
The application is a WPF Windows application, the Shutdown Mode is set to ShutDown when the main window is closed.
Now, I know that maybe Windows 10 is different and Visual Studio 2015 is different, but this is not a normal behavior in my opinion.
if you have any clue, maybe I've lost some new setting?
Thank you in advance
I was able to resolve the issue by doing a simple repair of Visual Studio installation.
I am currently working on a windows service, after installing the service via installutil.exe, as I start the service in services.msc there's no JIT window indication if I would want to debug it or not.
And once the service is running and tried the "Attached to process" in visual studio, It will say an error like Unable to attach to the process. Visual Studio has insufficient privileges to debug this process. To debug this process, Visual Studio must be run as an administrator. Eventhough I'm an administrator in my Local.
My problem is similar in this thread on MSDN thread.
But I am using Visual Studio 2008. I've tried all possible solution after posting this questiion here.
I've tried
adding <system.windows.forms jitdebugging=true/> to my config file
checking Tools->Options->Debugging
checking registry settings
run visual studio 2008 as administrator, attached the process and still throwing the insufficient priveleges error.
Any ideas?
I Hope someone could help me.
Thanks,
Sherwin
Just do what the error message is saying -- run Visual Studio as administrator. To do that, right click on Visual Studio icon in start menu and select option "Run as administrator".
I have a Visual Studio solution with roughly 90 projects in it (mixture of Windows Forms in C#/VB.NET,WPF and Silverlight stuff). I have a Windows Forms application (C#) as the startup app. I press F5 to start debugging.
When I exit the debugged application by selecting Stop Debugging in Visual Studio or by selecting Exit in the debugged application, Visual Studio continues the compilation of different assemblies. I have seen no pattern in what assemblies are compiled and it doesn't happen every time.
If I press F5 to start a debugging session, why would Visual Studio continue to build assemblies after I have finished debugging?
Maybe those assemblies that are compiled after your application launches do not affect your application and VS wants to launch your application as early as possible?
Have you checked your solution's Configuration Properties ? You can specify there which projects to be built.
Are you using Edit-and-continue? If so, it's rebuilding the edited assemblies.