MSPro.CLArgs 1.2104.12.1

2021-04-12

• Targets can now be used in a CommandContext.

  Previously, Targets were available in CommandLineArguments, only. This made it very inconvenient to use Targets with Commander.ExecuteCommand. Now you can specify a property in your CommandContext that will receive the targets specified in the command-line.

  class CommandContext
  {
    [Targets]
      public List<string> Directories { get; set; } = new();
      ...
  }
  

  (See again the CleanSolution CLArgs application example for using Targets)

• BETA Support for OptionTagValue ' ' to allow blanks as option-value separator, like /p "Parameter value" /x 5 instead of /p:"Parameter value" /x:5. Basically, this works; BETA because I haven't extensively tested all scenarios.

• Improved Settings to support help-text output for different consoles width': HelpAlignColumn and HelpFullWidth properties.

• Provides files ('@' token) are now found in the current (working) directory and then in the application's (exe) directory. This is extremely useful when you want to create Profiles.

Self-Contained Assemblies

• NO support for automatic Command resolution (AssemblyCommandResolver) with self-contained Assemblies, yet. more..

Command-Line Profiles

A Profile is a collection of predefined command-line arguments. You can store such profiles as global profiles in the Application (EXE) directory or you can override these global profiles by providing a local profiles in the current working directory.

If you store your application together with its global profiles, for example, here %LocalAppdata%\MSPro\Programs (don't forget to set a path to it), you can run CleanSolution.Exe @sln.profile from any working directory and apply the settings from the global profile stored with the application.