New answers tagged


I've seen it done with tabs after commas before so you get. {Reports.ReallyLongFoo, New ReportMetadata("Really Long Foo Report", PaperSize.A4, 8, 12, ...)}, {Reports.ShorterBar, New ReportMetadata("Shorter Bar Report", PaperSize.A4, 8, 14, ...)}, Unfortunately it fights against any automated formatting of the code block.


I like the idea of XML for simple things like this. If you restructure the XML the readability goes up. Something like this. Dim ReportConfigurations As XElement = <Reports> <Report> <name>Foo Report</name> <papaersize>A4</papaersize> <fontsize&...


I think the solution you have is the right one. If the report metadata is declared in one place, it seems like that would be fairly readable? However, one way to make it more readable would be to create a builder for the ReportMetaData class. Here's an example for Java (though should apply equally well to C#):


A simple format for storing tabular data is CSV. Attach it as a resource, just like you planned to do with the excel document. In theory you can even edit it using standard spreadsheed software, though there will problems with that: CSV does not encode types, so Excel will use heuristics to detect e.g. dates, which may corrupt data that looks like a ...

Top 50 recent answers are included