written December 27, 2015
OOPArgs1 is a library I wrote a while ago for parsing command-line arguments in C#. I'm considering writing someting simular for parsing configuraiton files. Why not using .NET's built in configuration?
- No control over where config files are saved, which can prevent portability or using config files for other purposes such as project files
- Config files are tied to version number of the application
- No management of loose data files
The project will be called OOPConfig and will be available as either a DLL or a single-file that can be easily included into projects. I've written several (unpublished) utilities in the former way, including Arguments2, the precursor to OOPArgs.
1: The name stands for Object-Oriented Programming Arguments, and is a play on OOPArts.