<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systemd on Coffee-Driven Development</title><link>https://duijzer.com/tags/systemd/</link><description>Recent content in Systemd on Coffee-Driven Development</description><generator>Hugo</generator><language>en-US</language><copyright>© {currentYear}, Jacob Duijzer. All rights reserved</copyright><lastBuildDate>Wed, 11 Aug 2021 12:25:11 +0200</lastBuildDate><atom:link href="https://duijzer.com/tags/systemd/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing a .NET Service with Blazor, on Windows and Linux</title><link>https://duijzer.com/posts/blazor-backend-service/</link><pubDate>Wed, 11 Aug 2021 12:25:11 +0200</pubDate><guid>https://duijzer.com/posts/blazor-backend-service/</guid><description>&lt;p&gt;My employee has developed an application which &amp;ldquo;scrapes&amp;rdquo; data from systems, processes it and sends it to a central database. This is a WinForms application with a few screens for configurations and inspections. I was looking into different approaches for a new version and dived into the options of using a Windows Service.&lt;/p&gt;
&lt;p&gt;I forgot where the exact idea came from but at a certain point I thought: what if I can install Blazor as a UI for a Windows Service. I could configure, start and stop, basically do all kind of things with this service if I have a Blazor Interface. I read something about systemd services with .NET too, so I could even create a cross-platform version (not that there is any need for Linux, but just because I can).&lt;/p&gt;
&lt;p&gt;Well, after a few hours, I got it working so, in this post I will show you how to create a cross-platform service that can be installed on Windows (Service) and Linux (systemd) and be managed with Blazor.&lt;/p&gt;</description></item></channel></rss>