This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

firefox 3.6.4 visual studio debug doesn't work

  • 2 (ردّان اثنان)
  • 18 have this problem
  • 1 view
  • آخر ردّ كتبه 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)

All Replies (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!