Houston We have a Problem with Silverlight Client OM…

So I was playing around with NavigationNodeCollection, which is basically like SPNavigationNodeCollection just to make sure it worked without a hitch…Here is a little sample snippet of what should work:

NavigationNodeCollectionClientOM

Unfortunately, you get a nice little javascript error that does not allow you to access the child nodes.  I tried a foreach() loop that gets a NavigationNode for each parent then loops through the NavigationNode.Children that did not work either.  I threw in two ExecuteQueryAsync statements thinking that would help, unfortunately adding a second statement provides no different results.  This appears to be a bug in the Silverlight Client Object Model.  I reported the error.  Hopefully, we get a fix by RTM so that we can use the easier method to get items into Silverlight, otherwise it’s back to WCF and cross domain policies.  We all love cross domain policies right?

Print | posted on Monday, March 08, 2010 5:43 PM

Feedback

# re: Houston We have a Problem with Silverlight Client OM…

Left by Praveen at 3/18/2010 4:36 PM
Gravatar Read more about the client object model and SharePoint 2010 here.
http://praveenbattula.blogspot.com/search/label/SharePoint%202010

# re: Houston We have a Problem with Silverlight Client OM…

Left by Praveen at 4/9/2010 3:02 PM
Gravatar Yes. Good catch.
http://praveenbattula.blogspot.com/search/label/SharePoint%202010

Your comment:





 
 

Copyright © MOSSLover

Design by Bartosz Brzezinski

Design by Phil Haack Based On A Design By Bartosz Brzezinski