[Valid RSS] This is a valid RSS feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="utf-16"?>
  2. <rss version="2.0" xmlns:atom="">
  3.  <channel>
  4.    <title>TeamVirtuoso Blog</title>
  5.    <link></link>
  6.    <description>TeamVirtuoso team blog.</description>
  7.    <lastBuildDate>Mon, 26 Jun 2017 03:41:13 GMT</lastBuildDate>
  8.    <pubDate>Mon, 26 Jun 2017 03:41:13 GMT</pubDate>
  9.    <language>en-us</language>
  10.    <atom:link href="" rel="self" type="application/rss+xml" />
  11.    <item>
  12.      <title>Unit Testing EFCore</title>
  13.      <link></link>
  14.      <guid></guid>
  15.      <description>Hi.</description>
  16.      <dc:creator xmlns:dc="">Eric Polerecky</dc:creator>
  17.      <pubDate>Fri, 26 May 2017 10:59:00 GMT</pubDate>
  18.    </item>
  19.    <item>
  20.      <title>The importance of .NET Core</title>
  21.      <link></link>
  22.      <guid></guid>
  23.      <description>Seven years ago, on 2010-04-12, Microsoft released a new version of .NET but unlike previous versions this version was not an “in place upgrade”. Meaning that for developers and IT departments to take advantage of this new version we needed to install the latest version on the server and developer desktops.
  25. Now, 7 years later, Microsoft is releasing a new version that requires developers and IT departments to manage these upcoming changes. But why? What is so significant about a new version of a programming framework? Why should our developers care? Why should our IT department deal with the upgrade headache?
  27. Lets also ask some larger questions, such as how does .NET Core position Microsoft in the developer platform wars and what does it means for the future of the platform?</description>
  28.      <dc:creator xmlns:dc="">Eric Polerecky</dc:creator>
  29.      <pubDate>Mon, 13 Feb 2017 12:07:00 GMT</pubDate>
  30.    </item>
  31.    <item>
  32.      <title>Echoing the Signal</title>
  33.      <link></link>
  34.      <guid></guid>
  35.      <description>We hope this post is but a drop in a sea of blog posts, internal emails to employees and open letters to the public from other companies, founders and leaders voicing their company's stance regarding the actions of the Trump administration.
  37. This is our statement and our offer to take action.</description>
  38.      <dc:creator xmlns:dc="">TeamVirtuoso</dc:creator>
  39.      <pubDate>Fri, 10 Feb 2017 11:40:00 GMT</pubDate>
  40.    </item>
  41.    <item>
  42.      <title>Visual Studio Code vs Sublime Text</title>
  43.      <link></link>
  44.      <guid></guid>
  45.      <description>Visual Studio code has been slowly gaining popularity since its announcement in April of 2015. Through my network of friends and coworkers, I'd heard more and more about it until finally it reached a point that I felt I should see what all the fuss was about. I've been an avid Sublime user for 4 years and it's given me everything I wanted in an editor (at least, until I saw what VS Code could do).</description>
  46.      <dc:creator xmlns:dc="">Jeremy Strawn</dc:creator>
  47.      <pubDate>Wed, 08 Feb 2017 11:00:00 GMT</pubDate>
  48.    </item>
  49.    <item>
  50.      <title>Work your Core… your .NET Core</title>
  51.      <link></link>
  52.      <guid></guid>
  53.      <description>I used to be embarrassed to tell my developer friends from the west coast that I was a C# developer. They all seemed to be working for trendy startups using cool hipster languages like Scala, Python and Go. Here I was, a lowly midwest developer doing enterprise consulting and writing stale C# code in a VM running on my macbook pro. Not exactly cool.  So what changed? Microsoft did. Microsoft changed. People say you can’t teach an old dog new tricks, but these days it seems like this old Microsoft dog has nothing but new tricks.</description>
  54.      <dc:creator xmlns:dc="">Breanna Turcsanyi</dc:creator>
  55.      <pubDate>Thu, 26 Jan 2017 13:14:00 GMT</pubDate>
  56.    </item>
  57.    <item>
  58.      <title>Migrating to dotnetcore, F# and mssql-server</title>
  59.      <link></link>
  60.      <guid></guid>
  61.      <description>During the week between Christmas and New Years we decided to migrate to dotnet core. Previously was powered by Jekyll, a static site generator that uses Ruby. Using Jekyll allowed me to get up and running quickly but now that we have time, and a few days off during the holidays, it's time to make our website an example of the work we do.</description>
  62.      <dc:creator xmlns:dc="">Eric Polerecky</dc:creator>
  63.      <pubDate>Tue, 03 Jan 2017 10:11:00 GMT</pubDate>
  64.    </item>
  65.    <item>
  66.      <title>ProTip: GO; != GO</title>
  67.      <link></link>
  68.      <guid></guid>
  69.      <description>Syntax matters</description>
  70.      <dc:creator xmlns:dc="">Eric Polerecky</dc:creator>
  71.      <pubDate>Mon, 19 Dec 2016 15:55:00 GMT</pubDate>
  72.    </item>
  73.    <item>
  74.      <title>Introducing TeamVirtuoso</title>
  75.      <link></link>
  76.      <guid></guid>
  77.      <description>Today, on September 17th 2016 I am very excited to announce the next evolution of .NET software development, coaching and consulting: TeamVirtuoso.</description>
  78.      <dc:creator xmlns:dc="">Eric Polerecky</dc:creator>
  79.      <pubDate>Sat, 17 Sep 2016 12:31:00 GMT</pubDate>
  80.    </item>
  81.  </channel>
  82. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda