CsvHelper VS Sylvan

I would also say either a logging framework or one of the many NuGet packages. Like CsvHelper.

I've been using CsvHelper for a long time and I quite like it. It's flexible and configurable enough to suit all my needs. Though the authors have unpleasant habit of introducing breaking changes (currently they are at major version 30).

It's really slow compared to (for example) csvhelper. I tried to use the built in microsoft stuff to handle a data transformation routine using excel files, turning them into csvs and using the csv library sped up the process from 3-4 minutes to about 8 seconds.

How might it compare to https://www.nuget.org/packages/CsvHelper/?

Let me guess, you replaced a string.Split(',') with CsvHelper?

I use CSVHelper https://joshclose.github.io/CsvHelper/ it has a WriteRecords function that will write out your objects

I would recommend looking at this popular library for reading / writing to csv files. https://joshclose.github.io/CsvHelper/

This is probably a bit churlish to complain about, since it's an entirely free tool that has saved me a lot of time and effort, but I'm baffled by the documentation for CsvHelper by Josh Close.

https://joshclose.github.io/CsvHelper/ is a good library for creating CSVs, but you need to tell us more about who is consumer of this export and may be there is a more direct approach

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.