syntaxsolutions/csvbuilder-net

A simple .Net library used to format data into comma-separated values (CSV)

csvbuilder-net's Issues

CsvRow.AddCell() throws exception on NULL input

When a null string is passed into CsvRow.AddCell() a "Object reference not set to an instance of an object" exception is thrown

Double quotes are not being escaped

Double quotes (") that appear in a cell are not being escaped

Update to RFC 4180 standard

Update so that data generated by GetBytes() adheres to the RFC 4180 standard

The RFC 4180 standard is defined as follows:

The technical standard RFC 4180 formalizes the CSV file format and defines the MIME type "text/csv" for handling of text-based fields. However, interpretation of the text of each field is still application-specific. Files that follow the RFC 4180 standard can simplify CSV exchange and should be widely portable. Among its requirements:

• MS-DOS-style lines that end with (CR/LF) characters (optional for the last line).
• An optional header record (there is no sure way to detect whether it is present, so care is required when importing).
• Each record "should" contain the same number of comma-separated fields.
• Any field may be quoted (with double quotes).
• Fields containing a line-break, double-quote or commas should be quoted. (If they are not, the file will likely be impossible to process correctly).
• A (double) quote character in a field must be represented by two (double) quote characters.

Optimise GetBytes() output

Reduce the size for the output generated by GetBytes()

• Only encapsulate fields with double quotes when required.

GetBytes() return 0 bytes when zero header and row count

GetBytes() should return null (0 bytes) if no data rows exist.