I am running Visual Studio 2013.
When I stop debugging my MVC application, IIS Express stops automatically. How can I stop this happening?
The trick is to right click on your website and View -> View in Browser (or just View in Browser for Visual Studio 2012).
This will start the website in IIS Express and keep it running, not dependent on a debugging session being run.
One option would be to launch IIS Express manually. I believe you can also just detach from process in visual studio instead of stopping the debug session.
In Visual Studio 2013, Go to Tools > Options
In Debugging menu in side list find Edit and Continue
Uncheck the Enable Edit and Continue check box
This will solve your problem
Related
I have deployed a solution on a server farm and wish to be able to debug the solution's logic whilst it is running on the server farm, since the problem resides in there, Is there any way or mean by which it is possible to debug a solution (.wsp) which was deployed on a server farm, through the visual studio?
You can either click F5 in Visual Studio and it will deploy the solution and attach a debugger to the appropriate SharePoint process. This can be a little slow but it allows you to debug your code.
You can also manually attach to the SharePoint process from Visual Studio. Go to Debug-->Attach to Process-->Check show processes from all users and sessions-->Select all w3wp.exe processes-->Click attach.
I have a visual studio solution with a half dozen web application projects. I often want to attach the debugger to a process. When I do this, visual studio always wants to start up cassini or IIS express or do something to run the web applications in the solution. Is there a way I can skip that, so when attaching to a process visual studio does not try to start the web applications in the current solution?
On the project properties, there's a setting called "Development Server" -> "Always Start When Debugging." Might be worth a shot.
I have been experiencing problems with Visual Studio 2010 and debugging.
I have been getting the:
"Unable to start debugging on the web server. The IIS worker process for the launched URL is not currently running." error, but it appears VS2010 now doesn't want to function at all and is hanging.
Whenever I try to attach the debugger, it doesn't.
If I try and run the project using the custom URL and letting IIS7 server the web page, the whole IDE is now hanging.
Has anyone had problems with the debugger not attaching, running the project with the debugger causing the above error and/or Visual Studio hanging completely when running the debugger?
I can't even minimise the IDE window and it seems to flicker when I click the button.
I have about four web projects that I am hosting in IIS Express. Whenever I do a build in Visual Studio 2010, the build will be blocked until I manually kill IIS Express. The build then completes. A new instance of IIS Express is created that works as expected.
I tried to do a prebuild event to kill IIS Express with taskkill, but the lock up seems to happen before the prebuild event is executed :/
If I stop the hosted sites, Visual Studio 2010 will also build as normal.
From research, one possibility is IIS Express is trying to display a dialog that Visual Studio 2010 is waiting for the user to interact with, but doesn't actually display the dialog.
Has anyone else had an issue with IIS Express and Visual Studio 2010 locking up on building? Or some insight on how to debug this issue?
If i remember correct the last service pack for vs 2010 corrected that error (at least on my maschine).
Sounds like visual studio is trying to do something on port 80, which IIS is blocking ( thats the default listener port for it ).
A simple google search of port 80 visual studio brings up several promising hits ( how to configure it, and hey! 2nd one even has a fix for a similar problem. )
This happens to me constantly, but then again I'm using WinXP / VS2010 / IIS Express 7.5. I suspect the WinXP part is the culprit, perhaps a bug for this particular scenario? At any rate, VS2010 wants to rebuild one of my web apps, but appears to wait indefinitely on some files in the Temporary ASP.net directory for the web app, until I stop IIS Express.
vsjitdebugger gets more annoying when i switched to windows 7. :(
i'm a commandline person (vim, msbuild and vsjitdebugger) when developing .NET. I'm looking for a better vsjitdebugger alternative that automatically attaches the application to visual studio (or any application that is less annoying than vsjitdebugger.)
TIA :)
From here
To begin Just-In-Time debugging when
an error occurs
In the Just-In-Time Debugging dialog
box, in the Possible Debuggers list,
click New instance of Visual Studio
2010 or click an instance of Visual
Studio 2010 that is already running.
To use Visual Studio automatically for
all future crashes, click Set the
currently selected debugger as the
default.
If you want to choose what types of
code you will be able to debug, click
Manually choose the debugging engines.
If you do not choose this option,
Visual Studio automatically selects
the appropriate debug engines for the
type of code in your program.
Click OK.