Reputation: 3508
I have problem to debug a simple Silverlight 2 application with Visual Studio 2008 SP 1. Sometimes, I could debug the Page.cs code and sometimes not. I have a web application, which hosts the silverlight .xap files.
Deleting the .xap files from ClientBin Directory and rebuilding works sporadic but not reliable.
I am frustrated.
Upvotes: 2
Views: 747
Reputation: 9088
I followed the advice on here and switched to Chrome. As Fayssal says it's the only process offering silverlight debugging.
I also uninstalled everything silveright off my PC (SDK, VS tools), and just installed the VS2008 Silverlight tools. See my versions here below.
Chrome also displays a dialog telling me that I'm on an old version of Silverlight. Which causes me problems with the silverlight detecting javascript I use. Turn that off with the command line arg --allow-outdated-plugins (more here).
..and you'll probably want to --disable-hang-monitor
Upvotes: 0
Reputation: 11
I use Chrome for debugging my Silverlight application without problems.
The only trick is that visual studio attaches itself to the wrong Chrome process when lauching the application. This could be solved easily after launching the application by choosing in visual studio Tools->Attach to Process -> (select the Chrome process that has "Silverlight" specified in its Type column, for me it is "Silverlight, x86")->Attach
Refreshing the application in Chrome should make the breakpoints hit in Visual Studio.
Upvotes: 1
Reputation: 3508
I found one very silly issue from myself: I have chosen Chrome as my standard browser. This is not the ideal browser, to develop silverlight apps.
Upvotes: 0
Reputation: 773
I see it frequently, too. What works always for me is to go to Web project property page, tab 'Silverlight Applications', delete the app and add it again. That seems to help 100% (ugly workaround, but...)
Upvotes: 3