azure-cost-cli VS CommandLineUtils

Hmm the Cost API works in mysterious ways. I noticed that different kinds of subscriptions can have different effects. On the github readme page I listed a way to lookup the subscription offer itself and how to validate that on the MS docs site to see what it supports. I will see if I can automate this somehow. Thanks for trying it out and reporting this. I think it might be the same issue as this one: https://github.com/mivano/azure-cost-cli/issues/25

The library doesn't support that format, here you can see that MultipleValues means for example "-o value1 -o value2" Options Support options with multiple values · Issue #311 · natemcmaster/CommandLineUtils · GitHub

You could roll your own with some command-line argument processing. You could write that yourself and use reflection, or for an example from a library I've used, example.

I want to test how my tools generated files and folders in the destination with different arguments passed to the program. However, in my old code, I put all the logic of working with arguments in the static int main( string[] args) function. I could not use Interface and Dependency injection to mock the CLI tools because CommandLineUtils does not have an interface library. Luckily, I found this guidance from the owner of CommandLineUtils, and he advised that "Split the command-line argument parser and application execution into separate class structures" to test various options programmatically. It is a great suggestion, and I rewrote my program by adding class CommandLineOptions and adding logic to class Generator to make it works with CommandLineOptions. I can kill two birds with one stone by this change: code refactoring and writing better tests. Another problem I had was my folder structure. Before, I put the project's sln file, .git file , and src files in the root of the folder. However, when I added a new test project for Shinny-SSG, I had it outside my git folder, and it would be impossible to commit the change and put it in my remote repository. To resolve this, I had to change my folder structure to this:

Thanks to https://github.com/natemcmaster/CommandLineUtils for supplying a lot of the command structures. If you're interested in creating your own dotnet tool, this is highly recommended.