<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ASP.NET Core on Throwin&#39; Exceptions</title>
    <link>https://throw.nullreference.io/categories/asp.net-core/</link>
    <description>Recent content in ASP.NET Core on Throwin&#39; Exceptions</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Copyright © 2020-{year} Elan Hasson. All Rights Reserved.</copyright>
    <lastBuildDate>Tue, 13 Sep 2022 02:07:52 +0000</lastBuildDate><atom:link href="https://throw.nullreference.io/categories/asp.net-core/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WebScheduler Part II: Designing the Web Scheduler</title>
      <link>https://throw.nullreference.io/posts/webscheduler-part-2-doing-the-design/</link>
      <pubDate>Tue, 13 Sep 2022 02:07:52 +0000</pubDate>
      
      <guid>https://throw.nullreference.io/posts/webscheduler-part-2-doing-the-design/</guid>
      <description>This is the second post in the series, if you haven&amp;rsquo;t read the first, you should stop here and read the first part before continuing.
This post covers the system design of the Web Scheduler and the decisions made during the design process.
The code for the project can be found here in these repositories .
The Tech Stack Hosting Platform: DigitalOcean&amp;rsquo;s App Platform Web Frontend Application: ASP.NET Core Blazor Frontend API: ASP.</description>
    </item>
    
  </channel>
</rss>
