Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

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

  • 2 отговора
  • 69 имат този проблем
  • 3 изгледи
  • Последен отговор от 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?

Всички отговори (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.