I use Firefox Developer Edition for all my development. But I would like DevTools to always be open when I start Firefox. Is there any way to do that? I know I can just hit F12 but it would be a nice feature.
I probably should have clarified a bit more...
What I was really trying to do was to get Visual Studio 2022 to automatically open Firefox DevEd with the DevTools open when I began debugging my VS project.
By default, VS will automatically open your chosen browser when debugging. However the Debug profile does not include a way to send the "-devtools" option to Firefox. (Or if it does, I couldn't find it.)
So I unchecked the "Launch Browser" setting in the Debug profile...
...and added "-devtools" to the Target item in the Firefox Properties panel.
So now when I debug my project, I just Run it then manually open Firefox. And it still supports Hot Reload if you have that enabled. This works pretty well but it would still be nice if you could send options/flags to your chosen browser. But this will work for now!
Related
Switching from Visual Studio 2015 to 2017 I find that launching a Web API project now starts a clean, separate Chrome window. For the most part I like that, and I certainly like the idea, however: this also means extensions are missing in Chrome.
Is there a way to start a Web API project from Visual Studio 2017 and have Chrome launch with extensions enabled?
Or, failing that, could I revert back to the old behavior where my project is opened as a fresh tab in my existing Chrome window?
I've tried Googling but found nothing. I checked the dropdown in Visual Studio with browsers (and checked the "Browse With..." dialog) but found no solution there either.
All you need to do is to sign-in to the instance of Chrome that VS2017 launches as the user you have all your usual extensions installed under (i.e. sign-in as the same user you usually sign-in as).
This sign-in "sticks", so extensions will load in the current - and all subsequent - debugging sessions.
You can revert back to the old behavior by
Debug > Options > Debugging > General > (uncheck) Enable JavaScript debugging for ASP.Net (Chrome and IE).
Is there a way to start a Web API project from Visual Studio 2017 and have Chrome launch with extensions enabled?
Yes, but it works for one project only, mean you need to re-install extensions when you launch a brand new project. I tried Sync in Chrome (not work).
In my opinion, there are something to do with Chrome remote debugging protocol profile. I hope someone knows about Chrome can give a final solution for this.
you can study more here: remote debugging protocol
There is a way that you no need to change anything. But it annoying.
Because Visual Studio 2017 use an instance of Chrome for debug mode when you hit F5, so you can leave that debug mode instance with remote debugging protocol open, and use your default Chrome instance with full extensions. Just copy and paste the link into your favorite Chrome instance.
Cheer! hope it help.
I have problem with debugging my web application from Visual Studio 2017.
I have selected Chrome as default web browser, even checked path to chrome.exe file and seems to be OK.
The problem is, that every time, when I'm starting debugging, it opens new instance of Chrome window, which seems to be completely clean. If I set some setting (for example, deselect "auto translate websites", at next debug session it is selected again.
Another thing is, that chrome session is loading without any plugins, and if I install a plugin during one session, it's not appearing at second one.
Anyone has solution for this problem?
From your VS2017, go to Tools, Options, Debugging, General.
Make sure that option for -Enable JavaScript debugging for ASP.NET (Chrome and IE)- is NOT checked.
When trying to debug a Silverlight 4 application in Visual Studio 2010 with Firefox as my browser, I am unable to hit any breakpoints. I get the message "breakpoint will not currently be hit".
Here is the solution that worked for me when debugging was not working in Firefox:
Type "about:config" into the address bar of Firefox
Find the property named "dom.ipc.plugins.enabled"
Change the value from true to false by double clicking
Restart all Firefox browsers
Go back to Visual Studio and start debugging!
Hope this saves someone else some time!
Firefox hosts silverlight (and other plugins) in a sandboxed process called plugin-helper.exe.
Manually attach your debugger to the correct instance of this (it'll have "Silverlight" in the process type field), and you get your debugging back, and you get to keep your plugin sandboxing too.
EDIT:
Looks like someone else sick of doing this by hand and wrote an VS2010 addon to automatically attach to plugin-helper.exe.
Suddenly today Visual Web Developer does not allow me to debug Silverlight applications.
This happens in 2008 and 2010 versions.
It gives no error message, just ignores all break points.
It can still debug ASP.NET applications.
Is anyone else experiencing this?
Added:
Interesting: debugging works in Internet Explorer but not in Firefox. Also on a new installation on a second computer it debugs in both IE and FF. Just noticed that that FF browser is still version 3.6.3.
I cleared everything in Firefox (3.6.4) but it still doesn't debug in that browser (on two computers):
alt text http://www.deviantsart.com/upload/l46lcc.png
While uninstalling the Silverlight plugin I saw this:
alt text http://www.deviantsart.com/upload/1i7j8ao.png
Check this link:
http://forums.silverlight.net/forums/t/188434.aspx
The solution seems to be:
Regarding the debugging: I think it
would be possible to write a VS plugin
or similar to attach to the
plugin-container.exe process
automatically, however there's a
simpler solution. You can disable the
new isolation feature in Firefox:
Type "about:config" into FF's address
bar Accept the warning (if applicable)
Search for the entry
"dom.ipc.plugins.enabled.npctrl.dll"
Change its value from "true" to
"false" (double-click) Restart the
browser
Mine seems to work fine in both VS2008 and 2010...
Would like to know if there is a setting anywhere which causes debugging to automatically stop when IE closes, and also if there is a way for this to work the other way around and IE to close if debugging stops.
I know that this works when the project type I'm working on is a 'Web Application', I'd like to know if the same functionality exists when working on a 'Web Site'
Thanks all.
This should be the default behavior of visual studio. i.e. , if you create a default asp.net website, and F5, then after you quit IE, VS automaticallly stops debugging. it doesn't work for aother browsers since these browsers don't have corresponding interface with VS.