<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>topshelf on Alastair&#39;s Blog</title>
    <link>https://alastaircrabtree.com/tags/topshelf/</link>
    <description>Recent content in topshelf on Alastair&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 29 Aug 2016 18:20:51 +0000</lastBuildDate>
    <atom:link href="https://alastaircrabtree.com/tags/topshelf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to run a dotnet windows service as a console app</title>
      <link>https://alastaircrabtree.com/posts/how-to-run-a-dotnet-windows-service-as-a-console-app/</link>
      <pubDate>Mon, 29 Aug 2016 18:20:51 +0000</pubDate>
      <guid>https://alastaircrabtree.com/posts/how-to-run-a-dotnet-windows-service-as-a-console-app/</guid>
      <description>C# Windows services can be a pain to develop because they are awkward to test, debug and run locally. However a few tweaks to the default VS template make them far more manageable.
Why use a windows service in the first place? At first glance a Windows Service looks like old tech in an age of http everywhere. However they are a reliable proven platform that is easy to deploy, easy to remotely monitor, and it is actually trivial to embed a web-server inside one and ditch IIS entirely.</description>
    </item>
  </channel>
</rss>
