Search

In the first part of the article I described the way to implement the deep linking feature in MVVM-based Silverlight application.

In this post I am going to describe two other important functionalities that  should be implemented to achieve great level of search engine optimization. First on is sitemaps and second one is html content providing.

In this post Jeremy Likness covers a lot of material - Prism and Silverlight, Dynamic Modules, Navigation...

I started a project to update my personal website using Silverlight. The goal is to use Prism/Composite Application Guidance to build out a nice site that demonstrates some Silverlight capabilities and make the source code available as a reference. One of the first pieces I chose to tackle was ensuring I could facilitate deep linking using Silverlight navigation and still take advantage of dynamic module loading using the Prism framework.

This error only appears in Silverlight 3 RTW, the previous beta versions did not have this “problem”.

Let’s take a look at what’s happening. Assume we have a Silverlight xaml file called MainPage and inside this page, we want to include navigation using a Frame.

Joel Neubeck is talking about using WritableBitmap for smooth transitions between the pages using Navigation Framework:

One thing that i thought was missing was the ability to  create nice looking transitions between pages as they are loaded into a frame.  Recently I voiced my complaint to a coworker and he had the great idea of using a WritableBitmap to capture the current and next page within the Frame, than animating the images.  Here is the solution I arrived at.

This is the first of a series of blogposts about the new features of Silverlight 3.0. It starts with the Navigation Framework introduced in Silverlight 3.0.

In the world of web we are used to passing urls to each other, so we always get the proper page without surfing through the whole website. Not to mention the search crawlers which access data (data in html pages) directly through these links. However with Flash and Silverlight this becomes a little more complicated. The navigation inside the Silverlight application is not tied to the browsers url field. You cannot reference a specific page in your silverlight application with a simple url. Or at least it would take a hell of a lot code to support it. Well, in Silverlight 3.0 we have the Navigation Framework which pretty much solves the problem stated above.

While working recently on a navigation application, there was this requirement for animated page transitions. Moving from one page to another must look pretty and if possible should include advanced animations with pages flying in, fading out, etc.

So I started investigating if and how this was possible with the navigation framework. And the answer is that it is very, very easy and it does not require a single line of code.

Jeff Prosise will show you how to use the Navigation Framework to allow forward and backward browsing to work.

A few weeks ago, I blogged about a sample application I wrote that uses Silverlight 3's WriteableBitmap class to draw views of the Mandelbrot set. I hadn't used it long before I realized that it really needed Back-button support. You could drill down into the Mandelbrot set, but you couldn't drill back out. Enabling the browser's Back and Forward buttons seemed a natural way to remedy the situation, but Silverlight and the Back button have never gotten along very well.

There are some new classes in the assembly System.Windows.Controls.Navigation.dll – specifically one called a Frame and a base class to derive from called Page along with some helpers of which the most key appears to be NavigationSource.

I built a little sample out of this. I wrote some .NET code that ran around my music library on my NAS and sucked out all the MP3 file information it could find and then I bundled that into an XML file and built a Silverlight app which shows that data.

This framework allows you to break your content into navigable chunks, or "pages," that derive from the new System.Windows.Controls.Page class. Pages are addressable by URI, just like pages in a conventional Web application, and the new System.Windows.Controls.Frame class provides an API for navigating among pages and integrating with the browser's history mechanism. One of the benefits of using the navigation framework is that it (gasp!) enables the browser's Back and Forward buttons. It also lends a degree of SEO friendliness to Silverlight since individual pages can be identified by URL.