Due to a design change in the Silverlight 4 installer you may see the following dialog when you attempt to debug:

This is due to the fact that the installer causes any older developer runtime to be upgraded when a newer client runtime installer is executed. As a result, the debugging components are uninstalled.
To fix this, please re-install the latest Silverlight developer runtime which can be found at via the following FWLink: http://go.microsoft.com/fwlink/?LinkID=188039
A fix for this will be considered during the SL5 timeframe.
Thanks,
–Mike







You had me at SL5
Hi Mike,
Do you know of a way to obtain a browser’s proxy information using the Silverlight API? The BrowserInformation class doesn’t give me this information.
cheers and keep the tips coming!
John
Awesome! I’d spent a while trying to figure this out and following (bad) old advise regarding the silverlight_chainer. Thanks for posting this useful info
Thanks everyone!
JC – I’ll post your question to our SL team and let you know if I get an answer.
Many thanks, Mike.
Hi Mike,
Good Stuff. Thanks for the post.
I tried to install the Developer runtime but running the installer I get:
Unable to install Silverlight.
The same version of Silverlight is already installed.
Thanks for help!!
.peter.gfader.
http://peitor.blogspot.com/
http://twitter.com/peitor
Can you try uninstalling your current version of the runtime before installing the latest? Let me know if that fixes it. Thanks.
JC – I did not receive a response about the proxy info. My guess is that it’s not supported. Sorry.
Thanks anyway, Mike. I can ‘work around’ that apparent limitation by using COM automation, although that route can obviously be fraught with problems…
Hi
There are 2 registry keys that are important for Silverlight debugging
Check
* HKLM,SOFTWARE\Microsoft\Silverlight\Components\Debugging
* HKLM\Software\Microsoft\.NETFramework\DbgpackShimPath
on 64bit
* HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Silverlight\Components\Debugging
* HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework
More here
http://peitor.blogspot.com/2010/04/no-debugging-in-silverlight-4-with.html
Excellent.!!!! I can work!! now!!!!!
thank you, thank you,thank you!
A fix is being considered? Do you have any idea how much time I lost today because I went to a Microsoft website that insisted I “upgrade” the client runtime, and then my Visual Studio quit working for running debug sessions.
If you guys need a cost justification to more the consider the fix, I will send you an invoice for my wasted time today.
Moderator, please ignore my previous comment. moment of frustration. At least I found this post eventually
Thanks Fixed it for me. you need to federate this infom more, this will likely make a few people mad.
Thank you Mike – back to work in seconds
Thanks to you and the gods of Google this fixed my issue. Appreciate it!
Thank you.
thanks, boss.
MS makes it so easy to break their setup.
Thanks a lot. Fixed my issue. Appreciate it!!!