<?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>Command Line on The Code-Mind Interface</title>
    <link>https://codemindinterface.com/tags/command-line/</link>
    <description>Recent content in Command Line on The Code-Mind Interface</description>
    <image>
      <title>The Code-Mind Interface</title>
      <url>https://codemindinterface.com/BowenCode_logo_blue-hi.png</url>
      <link>https://codemindinterface.com/BowenCode_logo_blue-hi.png</link>
    </image>
    <generator>Hugo -- 0.125.7</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Feb 2023 23:13:41 +0000</lastBuildDate>
    <atom:link href="https://codemindinterface.com/tags/command-line/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Structuring a Maintainable Console App with System.CommandLine</title>
      <link>https://codemindinterface.com/2023/02/system-commandline/</link>
      <pubDate>Fri, 24 Feb 2023 23:13:41 +0000</pubDate>
      <guid>https://codemindinterface.com/2023/02/system-commandline/</guid>
      <description>System.CommandLine as a Starting Point Writing console apps from scratch can involve a lot of messing around with boilerplate code just to get basic user input and take advantage of basic features like logging and configuration that come more or less for free in an AspNetCore web app. Adding in features normally found in command line apps like parsing input parameters commands and options or displaying help text to guide users adds on even more work before getting to the app&amp;rsquo;s core functionality.</description>
    </item>
  </channel>
</rss>
