Posts
-
New in the Silverlight 4 RC: XAML Features
Today, the Silverlight 4 RC was announced and made available to the masses. But you may be asking yourself: what’s new since the beta? Well, I’d like to dive into one of the areas where a bunch of new work was done to improve the development experience – the XAML Parser. With Silverlight 4, we’ve done a significant overhaul of the XAML Parser, allowing us to add new features and improve consistency within the platform and with WPF’s XAML support.
-
Silverlight 4 RC Announced at MIX 2010!
If you’re not watching already, head on over to http://live.visitmix.com to watch the keynote, where Scott Guthrie has just announced the Silverlight 4 RC!
-
On-demand loading of assemblies with Silverlight Navigation – Revisited for Silverlight 4 Beta
Way back in July, shortly after Silverlight 3 was released, I posted a technique that allowed you to use the Navigation framework in the SDK to load pages in dlls that would be downloaded as part of the navigation process. The solution relied on two things: a workaround to the navigation framework’s inability to navigate to Pages in dynamically-loaded assemblies, and a derived version of the Frame class that hid many methods in order to orchestrate downloads of dlls and their dependencies.
-
Opening up Silverlight 4 Navigation: Authentication/Authorization in an INavigationContentLoader
Continuing my series of posts on ways to use INavigationContentLoader (a feature in the Silverlight 4 Beta SDK), in this post, I’ll explore another idea for a composable INavigationContentLoader that protects access to your pages based upon the credentials of the user of your Silverlight application. To demonstrate its use, I’m using a WCF RIA Services application (purely for their Authentication/Authorization provisions).
-
Opening up Silverlight 4 Navigation: Event-based and Error-Handling INavigationContentLoaders
Last week, I gave an introduction to INavigationContentLoader, a Silverlight 4 Beta SDK extensibility point that allows you to load arbitrary content in conjunction with the Silverlight navigation feature, and walked you through building a Typename-based content loader. That’s all well and good, but it’s an awful lot of work to go to in order to build a simple INavigationContentLoader (following the async pattern, fully implementing the interface, etc.). Sometimes, all you really want to do is handle a few events in order to be up and running, fully integrated with Silverlight navigation. Furthermore, because of the nature of the feature, Navigation has a high potential for error conditions. For example, what happens if a user tries to follow a broken link or types a bad address into the browser’s address bar (with a browser-integrated frame)? How do you gracefully let your users know that something went wrong and give them some options about what to do next?
subscribe via RSS