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 check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…