Xaml and Media server controls

Fritz Onion has a post on his blog about these two controls. Unfortunately, my experiences with these controls didn't run very well and I don't agree with him when he says that they provide a cool model to integrate silverlight content on the page.

My main beef with them is that, unless they've changed something and have release a new version of the future bits, then those controls inject an object tag on the page instead of using js to create the new object on the fly (like the demo pages that come with silverlight do). The problem with this approach is that you get a "disabled" control which gives you a message saying that you must click to activate the control.

iAgain, it's one of those scenarios where i really can't understand why they're doing this when they've already have so cool js wrappers that could be easily embedded on the dll that has the control...

Filed under: ,

Comments

# Fritz Onion said:

Just to clarify, it's the concept of encapsulating Silverlight content in a control with embedded .xaml and .js resources that appeals to me. I also find the use of the <embed> tag slightly annoying in the asp:Xaml and asp:Media controls. The potential is there to build controls that create Silverlight content with the traditional script and then instrument it through properties, events, and methods - that's what's so compelling (in fact I just built one as a proof of concept).

 -Fritz

Tuesday, June 12, 2007 2:29 PM
# luisabreu said:

Hello Fritz.

yeah, i agree that the concept is good but, as i've said, the implementation sucks. Again, I'm not sure on why they simply didn't embed the silverlight.js file and generated the inserted a call  to the createSilverlight method...oh well, I believe that you're in a better place than me to get an answer to this question :)

Tuesday, June 12, 2007 3:54 PM

Leave a Comment

(required) 
(required) 
(optional)
(required)