Is there any concern against using Irony to create/alter the file on the specified format?
Our system is using a lot of various config files, and it would be nice for the .NET toolchain to have the format specified in just one place. For the whole CRUD on details within the parse tree.
Is the code that I would use for new'ing up the "parse tree" anywhere near as fluent as the code for grammar specification? Property initializers? Collection initializers?