Cursively VS Sylvan

I was looking at the CSV parser Cursively recently, and I think it is a good simple example of a high performance C# parser and API design.

https://github.com/airbreather/Cursively

Agreed, and agreed. #21 and #22 seek to address this, but these have actually been very low priority for me: as your benchmarks show, if you primarily need a bunch of objects that must be UTF-16 strings, then are other libraries out there that will do the job just fine. The main reason to use Cursively for that would be if you have some use cases where you need the unusual qualities that Cursively offers, but other use cases where you can live with something more traditional, and you don't want to have two different CSV processing libraries.

The usage instructions are in the README on https://github.com/airbreather/Cursively. The most straightforward way to get started (for now) is:

A while back I needed to process CSV with millions of records in a timescale of seconds. Sylvan Data was the best fit in terms of speed and memory efficiency. It might help you. https://github.com/MarkPflug/Sylvan

I maintain a couple libraries that aim to provide similar functionality to MTD: Sylvan.Data and Sylvan.Data.Csv.

Here is a simple, complete gist showing how to turn a DbDataReader into an HTML table. The WriteHtmlTable extension method can be used with any ADO.NET compatible driver, which the Sylvan.Data.Excel and Sylvan.Data.Csv libraries both support.

I maintain a couple libraries that can help with reading the data files: Sylvan.Data.Csv and Sylvan.Data.Excel. I see no reason to not allow users to provide whichever format is convenient for them.

I maintain a CSV library, Sylvan.Data.Csv, that shouldn't have any issue parsing this. You'll need to explicitly specify that space (' ') is the delimiter.

Here is a some sample code of how to echo the contents of an Excel spreadsheet as CSV to the client browser using my libraries Sylvan.Data.Excel and Sylvan.Data.Csv:

``` For reference, my implementation is here.

I maintain a couple libraries that should make this quite easy: Sylvan.Data.Csv, and Sylvan.Data.Excel. They are both open-source and MIT licensed. They are also both fastest-in-class at their particular tast.

Personally, I'd recommend Sylvan.Data.Csv, but being the author I'm probably a bit biased. Here is some CSV performance analysis that Joel Verhagen did for .NET libraries recently.