If I press the stop debugging button while debugging my ASP.NET Core app in Google Chrome it closes the Kestrel process window and the Chrome window that opens automatically on launching Debug. This is great and convenient!
Unfortunately it seems like Visual Studio closing Chrome in this way confuses Chrome and makes it think it has crashed. So every time I launch debugging in Visual Studio, a new Chrome window opens, and I see this annoying pop-up:
I found a similar issue brought up here, but it is for VS Code instead of VS2017. I don't think launch.json is a concept in VS2017 so I have no idea how to implement that workaround.
How can I prevent this from happening? Thanks!
Close all open Chrome windows
Edit file:
"%UserProfile%\AppData\Local\Google\Chrome\User Data\Default\Preferences"
Set:
"exit_type": "none"
and
"exited_cleanly":true
Change the Preferences file to readonly
not sure if this counts as an SO question, but lets give it a shot.
I have upgraded my Opera browser from v16 to the new chromium based browser (v18), and since then if I try debug an asp.net system in Opera Visual Studio throws up the following error
Unable to start program "http://localhost:3601/testpage.aspx. A null reference pointer was
passed to the stub
Has anyone hit this one before?
I have noticed the following
Everything runs as normal if I use IE or Chrome
If I run without debugging (ctrl+f5) the app runs fine
any suggestions? This is one of those silly things that is driving me nuts. I have tried reinstalling Opera, Visual studio. just seems like something isn't compatible
Thanks
System info: Win 7 x64 SP 1, IE 10, Visual Studio 2010
I've been researching this error all over.
visual studio debug error:
"unable to start program (File path) no more files"
This started with the installation of internet explorer 10 and is happening across all my web projects within Visual Studio 2010.
I've tried all possible solutions (but not VS re-installs) from registry entries (http://forums.asp.net/t/1891930.aspx/1), IE 10 reinstall (fail...won't let me reinstall due to existing version) to switching default launch browser (in Visual Studio, select a different browser such as Chrome to be default browser in "Browse With..." option in project..it works but is pain in the rear) but one thing I just tried which is making me wonder if there is an issue with how IE 10 is launched came from the following experiment:
Basically I did the same process of changing the default browser except that I picked IE 10 x86 version manually in the "Browse With..." option, set it as default and ran project. Voila, it works with no issues.
My next step was to confirm the default IE option in the "Browse With...". I found articles such as (http://lennybacon.com/post/2010/08/22/rehowtochangethedefaultbrowserinvisualstudioprogrammatically) which put me on the path to find out where the settings are for Visual Studios default browser settings.
I checked the browser.xml file and all looked ok including the registry entry pointing to it. I'm unable to check the version of the browser since MS, in it's infinite wisdom decided not to show that info in the Help -> About or anywhere else. so my gut feeling is that the default IE 10 being launched is the x64 bit version.
Does anyone know?
1) how I can confirm the default version of IE 10 launched since afore methods have not worked and
2) why would (I'm assuming) IE 10 x64 launch vs. the defined IE 10 x86 referenced version in the browser.xml file?
Thanks for any and all help.
Dave
UPDATE:
So from doing continual testing, it seems that after I ran the process to change the Default Browser settings in both the registry and the browser.xml file, upon launching the debug process in Visual Studio 2010, it automatically reverted back to the original default broswer settings which would launch the x64 version of IE 10. So in my case, it seems that the issue (error above) lies in the fact that debugging in Visual Studio 2010 using x64 browsers would cause the error. With no recourse, I ended up removing IE 10 from Windows Features and going through a painful process of getting IE 9 back on my system, I now can effectively debug using IE (x86).
It seems that MS is not pursuing any fixes for this issue of the default browser in VS 2010 from what I've read. There are in browser tools I've seen to do the default browser setting changes but don't want to bother with it/don't trust it will work.
Hopfully this helps others dealing with the same pain I have endured...
Thanks
Dave
When I ran into this problem (using IE 11) I noticed that iexplore was open about a hundred times in the task manager. After killing them all I was able to open my project just fine.
Since then, I have made a .bat file with this code: taskkill /F /IM iexplore.exe /T
so now I just run the .bat when I get that error. (alternatively you could run that code from the cmd)
James Butler's response is good for killing all the open IE processes. Which seems to be the issue here. The best solution I have been using is to just set, "Don't open a page. Wait for a request from an external application." then I just refresh the URL (if already open in browser) each time I rerun the debugger.
Access in Project properties under the, "Web" option. Then change setting there.
Check the following registry key
HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\TabProcGrowth
Make sure that the value is Minimum
I started getting this error today after restarting from a Windows Update. I'm on Windows 8.1 desktop using VS.NET 2013. To fix I had to add another browser choice in VS debug that was pointing to the x86 version of IE11, and set that as the default. Although the post alludes to the x64 vs x86 browsers being the issue, this seems like an easier solution than the original poster's process of uninstalling and reinstalling browsers.
This blog explains how to set the default browser for debugging to IE x86: http://weblogs.asp.net/gurusarkar/visual-studio-web-developer-express-starting-two-instances-of-internet-explorer-and-throwing-an-error
Have you tried this: "...try selecting the project node in Solution Explorer and choose Set as StartUp Project". Just worked for me.
https://social.msdn.microsoft.com/Forums/en-US/efd93f22-1f1f-4fb1-8ff3-e29104780572/unable-to-start-program-there-are-no-more-files?forum=lightswitchgeneral
I think this is caused by a more general issue of low available system memory. In my case, Performance Monitor showed I was using 82% of my available memory when I was receiving the error. Looking at the processes, the culprit for me was lots of Chrome processes. I shut down Chrome, which freed up about 2 GB of memory, and then I was able to run the debugger successfully. Shutting down lots of IE processes would achieve the same thing of freeing up lots of memory. So I think the solution is just to free up system memory by shutting down whatever processes you don't need open.
This is what is working for me with windows 11 and edge:
Project Start Options - Don't open a page. Wait for a request from an
external application.
Start - Local IIS (Microsoft Edge)/Script
debugging disabled
Create a shortcut to launch the application like
this: "C:\Program Files (x86)\Internet Explorer\iexplore.exe"
http://localhost/MyApplication/
I just changed from a linux/apache2.0/php4 web server to a windows/iis7/php5 web server (I only post php versions since that was a significant change).
My css is working just fine on the linux one (http://66.119.8.165/flcunderconstruction.php) but it isn't working on the windows one (http://66.119.8.236/flcunderconstruction.php).
Now, the issue only seems to be applicable to internet explorer 8 (maybe older, but I'm not testing those). Firefox and internet explorer 9 work just fine.
I think I've ruled out php issues as I created a non-php version (http://66.119.8.236/flcunderconstruction.html) and the issue persists.
I'm assuming the problem is in the css (which is quite large and throws up a lot of validation errors). But since it only occurs on the windows server and with ie8, I'm hesitant to start whacking away at the code.
Any ideas?
JJ
The broken version stops loading when it hits /include/html5.js. You only see this on IE8 because later versions handle the HTML5 stuff just fine without the polyfill.
Missing: http://66.119.8.236/include/html5.js
Present: http://66.119.8.165/include/html5.js
To test this, press F12 to open up the Developer Tools. Switch your Browser Mode to IE8. Jump over to your Network tab and press "Start Capturing". Perform a hard refresh (CTRL+F5), and watch as the files begin loading in. You'll note the 404 when it gets to the HTML5 polyfill. (Image below)
Using Fiddler2, I set up and Auto Responder to automatically add the HTML5 file from my local machine in the place of your missing file. Refreshing the request resulted in the entire site loading as expected in IE8. Put your polyfill on the other server, and you should be set.
Visual Studio has integrated debugging in IE, when you close IE, it stops debugging, and if you stop debugging, VS closes IE.
I want it to do the same thing with firefox/chrome! (mainly this 2, if is it possible with others, it'll be appreciated!)
Is there a way to do this?
Thanks in advance!
You need to change Visual Studio's default browser to Firefox/Chrome. To change this setting, right-click on an aspx file in Solution Explorer and select Browse With. Select the desired browser and set it as default.
What you need is to write a macro that opens up ff (or any other browser) with the debugging url.
Then you can control it and close it when the debugging ends.
but i think this task is quite hard to implement.
who mentioned here to simply set the default debug browser is not answering your question at all, b/c it will not be closed...
With Firefox established as your default browser and Firebug installed, you can debug your script in Firefox. Select Tools > Firebug > Open Firebug. The Firefox instance now shows the debugging console. To enable script debugging, click the Console tab, check the Script option, and click the "Apply settings for localhost" option.