Овај сајт ће имати ограничену функционалност док га будемо ажурирали у циљу побољшања вашег искуства. Ако неки чланак не реши ваш проблем и желите да поставите питање, на располагању ће вам бити наше заједнице подршке @FirefoxSupport на Twitter-у и /r/firefox на Reddit-у.

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

firefox 3.6.4 visual studio debug doesn't work

  • 2 одговорa
  • 18 има овај проблем
  • 1 преглед
  • Последњи одговор послао AnonymousUser

more options

I'm developping a web application in silverlight. I've never having a problem with silverlight or firefox since 1years. But 2 days ago i download FF 3.6.4 and then i can't debug my web app anymore ! I've spend 4hours to reset my setting in visual studio, try older project etc. Then i try to put IE as standard web browser, then it works with IE ! The same for chrome !

Firefox is loved by developpers, if they can not debug their application, they will move to another browser, even they got dozen awesome plugin :(

This happened

Every time Firefox opened

== I start debuging my web application (silverlight)

I'm developping a web application in silverlight. I've never having a problem with silverlight or firefox since 1years. But 2 days ago i download FF 3.6.4 and then i can't debug my web app anymore ! I've spend 4hours to reset my setting in visual studio, try older project etc. Then i try to put IE as standard web browser, then it works with IE ! The same for chrome ! Firefox is loved by developpers, if they can not debug their application, they will move to another browser, even they got dozen awesome plugin :( == This happened == Every time Firefox opened == I start debuging my web application (silverlight)

Сви одговори (2)

more options

Check http://forums.silverlight.net/forums/.../188434.aspx. 3.6.4's new plugin model causes the problem but there is a workaround for now.

more options

I ran exactly into the same trouble, 4 hours of troubleshooting!