when i debug my ASP.NET application / website in visual studio , after closing browser window ,debugging not stop and IIS Express Still working.
how can i stop debugging after close browser
i am develop my program in visual studio 2012 SP1
Closing the browser window in Visual Studio 2012 will detach the debugger. If the ASP.NET development [web] server is still running after you do that, you can always right click on it in the system tray and select "stop".
Related
created a new web application with one webform for testing. have windows 10, visual studio 2015 community edition.
if i use internet explorer to open/debug the project and just CLOSE the internet explorer, then my debugger in visual studio does stop.
if i use edge to open/debug the project and then CLOSE the edge, my debugger keeps running.
bug? can i reach that the debugger also will stop when closing EDGE?
I have an ASP.NET MVC 4.0 web project. I am caching state in the application cache using the Ninject InSingletonScope.
Every time I start Visual Studio 2012 debugging (F5), it kills my web app and my app cache also.
Note that I use IIS and not IIS Express, and I don't use Edit and Continue (see Visual studio debugger, dont stop website on stop debugging)
How can I prevent VS to stop my website every time ?
Instead of pressing F5, try going to the menu: Debug -> Attach To Process and attach to w3wp.exe for the website that is hosted on IIS.
When debugging web applications, VS2012 is opening two browser windows. One to my application and another to 0.0.0.1.
Any clue as to why and how I can stop it. It's pretty annoying having to close that window every time I debug.
I want to use iis express with vs 2010 but i can't install sp1 for now, i have figured out how to do this, it is close to this guide How to configure Visual Studio 2008 to use IIS Express? and it works.
My problem is that when vs runs iisexpress it has also an annoying command window (besides the tray icon) which i would like to get rid off.
I can't install sp1 for vs 2010 but i have installed vs 2010 express with sp1 and double checked that when the integrated iis express option is used it runs without command window
First thing i've done was to check if iis express has some command line options to hide the window, but no luck, on the other site option integrated in sp1 can run without this windows, so...
how to do this the same way / or how the sp1 option is doing this ?
p.s. There is however one catch, if vs runs iis express and you wait couple of seconds and then go to tray-> choose website and click Stop Site the command window disappears but iis still runs and the site also, i don't know if this is a bug or something, but then it is like in sp1 no window, only tray icon.
There is no command line option to disable command window, but you can use /systray command line option to disable tray icon.
Visual Studio uses CreateProcess API (or similar API) with creation flag set to CREATE_NO_WINDOW (0x08000000). Following links may help you!
http://msdn.microsoft.com/en-us/library/ms682425(VS.85).aspx
http://msdn.microsoft.com/en-us/library/ms684863(VS.85).aspx
Your observation is due to the fact that VS has attached to iisexpress.exe (when you stopped site from tray icon, iisexpress is in the process of shutdown by closing it's console window etc..., but since VS is attached to it, iisexpress is not able to exit and running in the background and waiting for VS to release)
I have an ASP.Net Web Site with GridView control that in turn contains a ButtonField column. It's supposed to do a postback when this ButtonField is clicked, but that doesn't happen if I click on the button from within the Internet Explorer window that Visual Studio opens while debugging. I can get it to successfully postback when I bring up and click on the ButtonField from an externally-invoked Internet Explorer window or a Firefox window, but never from the window Visual Studio produces.
I'm using:
Windows Vista Home Premium
Visual Studio 2008, running as Administrator
Internet Explorer 7.0.6000.16809
Firefox 3.0.6
Do you have any javascript added to that button? If javascript fails onclick it could bring up the debugger when running via VS but any other browser might just be eating the error.
I've determined the problem is due to running Visual Studio 2008 as Administrator under Windows Vista. Doing so causes some kind of issue with Javascript that prevents GridView ButtonFields from issuing postbacks. Contrary to Microsoft's advice for the previous version of Visual Studio (2005), debugging with Visual Studio 2008 running under Windows Vista requires that the IDE not be run using "Run as Administrator".