Blog » Integrating a Blogger Atom Feed into an ASP.Net MVC Application › IQODE Limited. Consuming RSS Feed in MVC ASP.NET. Introduction In this article, i will build a MVC application that will consume an RSS feed.
I will modify my previous project for RSS Feed. Follow the these steps. Select the "Controllers" Folder and then right click and click on Controller as shown below. Press Add, and RssFeedController class will be created as shown below. Repeat the above step 2, and Add RSSFeed view in Views\RSSFeed folder. Now you can run the project and it will display rss feed from weblogs.asp.net as shown below. Summary In this article, we built an RSS Feed application using System.ServiceModel.Syndicatation namespace. CodeProject Farooq Kaiser Software Developer (Senior) 12+ years of complete software development life cycle experience for web based applications and multi-tier client-server desktop, primarily using LINQ, WCF, WWF, C#, ASP.NET, XML, XSLT, AJAX, Winforms,Visual Basic, JavaScript, JQuery, Google APIs, C++, VB.NET, C, ATL/COM, Open XML.
Using SyndicationFeed class to create and read RSS/Atom feeds. Publishing content with AtomPub and ASP.NET Web API - Part 1 - ben foster. Recently I've been working on an API for fabrik (a portfolio and blogging service).
Since no GUI clients exist yet for the API (because I haven't developed any) I thought it would be useful to support a standard publishing protocol, especially since ASP.NET Web API makes this so easy with content negotiation. In the past I've used MetaWeblog API. Unfortunately MetaWeblog API is a RPC based protocol (XML-RPC to be exact). XML-RPC requires that we construct special XML requests to invoke specific functions on the server.
In the case of the MetaWeblog API, we have the following basic entry-points: metaWeblog.newPost (blogid, username, password, struct, publish) metaWeblog.editPost (postid, username, password, struct, publish) metaWeblog.getPost (postid, username, password) Since I'm building a REST API, I needed a protocol that adheres to REST principles. The Atom Publishing Protocol (APP) is based on HTTP and is used for publications and posting on Web resources. Listing Collection Members. Create RSS and Atom feeds using custom ASP.Net MVC Action Results and the Microsoft Syndication classes - Sean McAlinden's Blog. There are many ways to create RSS and Atom feeds, in this post I’m going to show one way of creating a re-usable solution that utilises the Syndication classes from the System.ServiceModel.Web assembly.
To make good use of the ASP.Net MVC framework I am going to show a nice way of creating custom action result methods to return the feeds without the need for creating any views. As this is quite a detailed overview with a fair amount of code – you can download a working solution here. The first thing to do is create the custom ActionResult methods to return our feeds. Aggregating RSS Feeds in C# and ASP.NET MVC 3Wade Wegner.
I’m working on a Windows Phone project that requires me to surface up multiple RSS feeds as a single source.
I needed a way to do this quickly and easily, and with a little help from friends on Twitter (particularly a suggestion from @bertcraven) I found a nice way to accomplish this using the SyndicationFeed in System.ServiceModel.Syndication. I’ve detailed the steps below, but if you want to get to the heart of it then here’s the code to get this working: It’s really quite simple – once you know how to do it!
As you iterate through the list of feeds we use LINQ to union the feeds together – in the end this produces a main feed that has all the contents. Along the way we sort the elements in a descending order based on the PublishDate – otherwise you’ll just get blocks from each of the feeds and nothing is sorted according to the date publish. Rss feed formatter ActionResult for ASP.NET MVC. Creating RSS feeds in ASP.NET MVC. ASP.NET MVC is the technology that brought me to Microsoft and the west-coast and it’s been fun getting to grips with it these last few weeks.
Last week I needed to expose RSS feeds and checked out some examples online but was very disappointed. If you find yourself contemplating writing code to solve technical problems rather than the specific business domain you work in you owe it to your employer and fellow developers to see what exists before churning out code to solve it. The primary excuse (and I admit to using it myself) is “X is too bloated, I only need a subset. I can write that quicker than learn their solution.” but a quick reality check: Time – code always takes longer than you thinkBloat – indicates the problem is more complex than you realizeGrowth – todays requirements will grow tomorrowMaintenance – fixing code outside your business domainIsolation – nobody coming in will know your home-grown solution This also has a few additional advantages: [)amien.