Search
MSN Status
(loading)
Recent Posts
Popular Posts
Sites Worth A Visit
Blog Syndication
Silverlight Spy for Beta 2 available
I just finished uploading an updated version of the Silverlight Spy which is capable of spying on Silverlight 2 Beta 2 applications. The list of changes:
- Fully supports Beta 2
- XAML Explorer provides a complete overview of an application's object tree. In Beta 1 it wasn't possible to fully explore the object tree, now it can thanks to VisualTreeHelper.
- New Beta 2 font related properties available on types derived from Control.
- Various minor updates to get things running smoothly
Important note: This Spy version requires an updated csExWB browser control. Although I use ClickOnce technology here, this COM setup somehow doesn't seem to notice there is a new version available. Uninstall your current csExWB browser version first, before trying to run the new version of the Silverlight Spy.
7 Comments
Rodrigo Ratan said:
In the download page it lists SLB1 as pre-requisite. I think this can mislead someone thinking that this is not silverlight 2 beta2 compatible (no mention to slb2 there). Just a tip :)
Koen said:
Thanks for the heads up Rodrigo. Fixed it.
Boon said:
For some reason, Spy sees all the SL2 b2 apps that I deploy on my development server as Silverlight 1.0 applications. This is despite the the fact that the silverlight configuration dialog box shows the beta 2 build... Anyone else running into this?
Koen said:
Boon: I've just updated the Silverlight Spy FAQ section which might answer your question. Take a look at http://firstfloorsoftware.com/silverlightspy/frequently-asked-questions/#q7.
Boon said:
Actually, I already had the minimum version attribute set correctly. It looks like the problem was the "Version" attribute (in the aspx) was missing.
So, in the aspx file, you need to have both the MinimumVersion="2.0.30523" and the Version="2.0" attributes.
Thanks for the help!
Boon said:
I retract my comment above... setting the Version="2.0" tag breaks the app. Setting the minimum version tag alone is insufficient to make spy work.
The main difference between the generated html between the aspx and the html page (that works) seems to be the tag that says type="application/x-silverlight-2-b2". ASPX turns this into type="application/x-silverlight" without the 2-b2 part. This is not directly settable in the aspx file, and I've yet to come up with a way to tinker with it and make it work.
Suggestions appreciated.
Koen said:
I think updating the Spy should help. I will modify the Silverlight application discovery routine, so it will try to include applications of the wrong type. I'll try to include this behavior in the next release of the Spy.
