How to Ingest an RSS Feed in Silverlight


In this article we will learn how to consume an RSS feed in Silverlight. Additionally we will also look into fetching the results and binding them onto the Silverlight DataGrid. Sample source codes have also been included in this article for demonstration purpose.

For the sample application I have used Visual Studio 2010 and Silverlight 4.0.

Importance of RSS Feeds

In recent days most of the popular websites, for example even the Microsoft websites, provided all the updates and new information through publishing RSS feeds. Hence in most applications that are developed, the ingestion of the RSS feed has become almost inevitable. This will facilitate the client application to process and display the feed content.

So I thought it would be informative to write an article on ingesting an RSS feed in a Silverlight application.

Supporting Classes in Silverlight

Silverlight is packed with some supporting classes for the RSS feed ingestion and processing. The namespace to include for making use of these classes is System.ServiceModel.Syndication. Some of the classes are listed below.

  • SysdicationContent
  • SyndicationFeed
  • SyndicationItem, etc.

The RSS feed response from the given RSS Uri needs to be fetched using the WebClient class and these syndication classes are for easy parsing of the RSS feed content.

Sample Code

Create a sample Silverlight application and name it as RSSFeedIngestionDemo. In the MainPage.xaml define a textbox, a button and a Silverlight DataGrid. So the idea for the sample application is to provide the RSS feed url in the textbox and clicking on the button would fetch the response, parse it and bind the content onto the DataGrid.

Below is the XAML code for MainPage.xaml.

d:DesignHeight="422" d:DesignWidth="581" xmlns:sdk="">

Below is the code behind implementation in MainPage.xaml.cs file.

namespace RSSFeedIngestionDemo
public partial class MainPage : UserControl
WebClient _webClient = null;
public MainPage()
_webClient = new WebClient();
_webClient.OpenReadCompleted += new OpenReadCompletedEventHandler(webClient_OpenReadCompleted);
private void GetResponseButton_Click(object sender, RoutedEventArgs e)
_webClient.OpenReadAsync(new Uri(UriTextBox.Text, UriKind.Absolute));
void webClient_OpenReadCompleted(object sender, OpenReadCompletedEventArgs e)
if (e.Error == null)
SyndicationFeed syndicationFeed = SyndicationFeed.Load(XmlReader.Create(e.Result));
var feeds = from feedItem in syndicationFeed.Items
select new
Title = feedItem.Title,
Content = feedItem.Summary.Text,
NavigateUri = feedItem.Links.FirstOrDefault().BaseUri.AbsoluteUri,
PublishedDate = feedItem.PublishDate,
LastUpdated = feedItem.LastUpdatedTime
RssResultsGrid.ItemsSource = feeds;
MessageBox.Show(string.Format("RSS feed ingestion failed. Failure Message: {0}", e.Error.Message));

In the above code, the WebClient class is used to fetch the XML response from the given RSS feed Uri. Then the response XML is loaded into the SyndicationFeed object where the SyndicationFeed.Load(xmlResponse) takes care of parsing the XML data and populating the SyndicationFeed object.

Now go ahead and run the sample application. Input a valid RSS Uri and click on the Get Response button. The result is bound to the Silverlight DataGrid.


Hope this article provides a clear overview of ingesting an RSS service in Silverlight. Please make use of the comments section to provide your comments.

About the Author

V.N.S Arun

I work for an MNC in Bangalore, India. I am fond of writing articles, posting answers in forums and submitting tips in dotnet. To contact me please feel free to make use of the "Send Email" option next to the display name.

Related Articles


  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Enterprises are increasingly looking to platform as a service (PaaS) to lower their costs and speed their time to market for new applications. Developing, deploying, and managing applications in the cloud eliminates the time and expense of managing a physical infrastructure to support them. PaaS offerings must deliver additional long-term benefits, such as a lower total cost of ownership (TCO), rapid scalability, and ease of integration, all while providing robust security and availability. This report …

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date