Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Is it possible to use Firefox to debug javascript files when running a web application using visual studio 2010

  • 2 odpovědi
  • 69 má tento problém
  • 19 zobrazení
  • Poslední odpověď od Naor

more options

I am trying to debug a ASP.Net web application within visual studio 2010 using Firefox. I am able to set breakpoints in my C# code and they work but if I set a breakpoint in a javascript file then these do not work when using Firefox. Is there any way to do this?

I am trying to debug a ASP.Net web application within visual studio 2010 using Firefox. I am able to set breakpoints in my C# code and they work but if I set a breakpoint in a javascript file then these do not work when using Firefox. Is there any way to do this?

Všechny odpovědi (2)

more options

Of course you can. I use the VS2010 built-in Javascript debug tool a lot, not only for IE, but also for firefox.

I encountered the "break point not working" issue several times, according to my experience, following is the solution to this problem, give them a shot:

1. There maybe errors in your javascript code, have a close look at your code, try to find the errors or eliminate this possibility.

2. Sometimes you have to refresh the page once after the page is loaded the first time. This solves the problem most of the time.

more options

How do you do that? I don't believe you can. maybe you confuse with server debug. I need to debug Javascript code in wisual studio where firefox is my default browser. VS2010 doesn't load the symbols for the JS debug. I stuck with the dumb internet explorer 8 debugger.