I started a new asp.net website yesterday vb.net ; I am familiar with VB.NET, but not with ASP.NET.
My main browser is Google Chrome, but when I try to "emulate" (debug) a site, the debugger exits the local development server generated by Visual Studio, and as a result, Chrome can never load the website (since when it Web server attempts fail). This can be easily seen by looking at Chrome and Visual Studio side by side; The Visual Studio status bar turns orange for a second or so, then returns to blue, and IIS exits with code 0 :
The program '[73048] iisexpress.exe: Program Trace' has exited with code 0 (0x0). The program '[73048] iisexpress.exe' has exited with code 0 (0x0).
However, this can be temporarily fixed by "emulating" in Internet Explorer and then with Chrome again, but this fix must be applied at every reboot in order for it to work.
Why is this happening, and how can I properly debug in Chrome without a web server coming out?
I am reading How can I prevent Visual Studio 2013 from closing the IIS Express application when debugging is complete? , but none of the solutions helped me in this regard, and that the problem is that Visual Studio closes iisexpress.exe when starting debugging.
Chrome launches each tab in a separate process (sandbox), so is it possible that Visual Studio expects a base PID from Chrome when Chrome actually generates a completely new PID for a new tab created when the emulator starts?
Is there any solution for this other than using Internet Explorer (or "fix") to debug the site?
I recorded what happens here, and it still seems strange to me that Internet Explorer can "cure" the problem temporarily.
I am using Visual Studio 2013 Ultimate with Windows 8.1 Pro (Media Center Edition) and Chrome 40.0.2214.93 m.