Skip to main content

How to access RSS feeds from code

.NET ne permite sa accesam feed-uri in format RSS sau ATOM fara nici o problema. XML returnat de un RSS nu trebuie sa il procesam noi manual, exista deja clase in .NET care pot sa faca acest lucru.
In postul de astazi o sa ne vedem cum putem sa incarcam un feed de tip RSS din cod.
Dupa cum stiti, formatul unui feed RSS este XML. Acest format este deja standardizat si nu ar trebui sa ne trezim cu campuri noi. In general un feed RSS contine date despre cine ne furnizeaza aceste date precum titlu, descriere, link, data publicarii, etc. Iar fiecare element( feed) contine: titlu, descriere, id unic( GUID), descriere si data publicarii. Mai jos puteti sa gasiti un exemplu de fisier RSS versiunea 2.0 care contine un singur feed:
<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
<title>RSS Title</title>
<description>This is an example of an RSS feed</description>
<link>http://www.someexamplerssdomain.com/main.html</link>
<lastBuildDate>Mon, 06 Sep 2010 00:01:00 +0000 </lastBuildDate>
<pubDate>Mon, 06 Sep 2009 16:45:00 +0000 </pubDate>
<ttl>1800</ttl>

<item>
<title>Example entry</title>
<description>Here is some text containing an interesting description.</description>
<link>http://www.wikipedia.org/</link>
<guid>unique string per item</guid>
<pubDate>Mon, 06 Sep 2009 16:45:00 +0000 </pubDate>
</item>

</channel>
</rss>
Sursa: http://en.wikipedia.org/wiki/RSS#Example
O varianta simpla de a accesa aceasta informatie, este facem un request spre adresa URL care ne returneaza aceste date, iar apoi folosindu-ne de clasa SyndicationFeed putem sa incarcam si sa accesam aceste date ca si niste feed-uri.
Primul pas este obtinem datele in format XML. Pentru acest lucru putem sa ne folosim de clasa WebClient, prin intermediul careia putem sa obtinem continul returnat de orice adresa URL.
WebClient webClient = new WebClient();
string rssResult = webClient.DownloadString(rssUrl);
Folosind metoda DownloadString, continutul returnat de catre URL dat se va copia local ca si un string. WebClient ne mai permite sa copiem continutul si ca si un sir de bytes( DownloadData) sau sa copiem continutul direct intr-un fisier( DownloadFile). Aceasta actiune se poate face atat sincron cat si asincron.
Pentru a putea accesa aceste resurse, WebClient tine cateva resurse legate de retea blocate. Din aceasta cauza este bine sa facem dispose la instanta unui obiect de tip WebClient, cand nu mai avem nevoie de el.
string rssResult = null;
using(WebClient webClient = new WebClient())
{
rssResult = webClient.DownloadString(rssUrl);
}
Odata ce avem rssResult, putem sa incarcam rezultatul folosindune de SyndicationFeed. Prin intermediul acestei clase putem sa cream noi feed-uri RSS sau ATOM, dar putem sa si incarcam feed-uri RSS deja existente.
SyndicationFeed feed = SyndicationFeed.Load( rssResult );
Din acest moment, folosindu-ne de obiectul feed, putem sa accesam orice date in felul urmator:
feed.Title
feed.Description
feed.Id
Fiecare item poate sa fie gasit sub propietatea Items, care contine o colectie de obiecte de tip SyndicationItem. Fiecare element de acest tip o sa contina date despre "stirea" curenta.
SyndicationItem item = feed.Item.First();
... = item.Title;
... = item.Description;
In acest post am vazut o modalitate prin care putem accesa un RSS feed folosind WebClient si SyndicationFeed.
Enjoy!

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...