Enums.NET VS CsvHelper

If you deal with Enums regularly, Enum.NET is a must have: https://github.com/TylerBrinkley/Enums.NET.

I guess you use a reflection-based library / nuget package to read those attributes. You can still do this in F#. The equivalent declaration and how to read it back using [Enums.Net](https://www.nuget.org/packages/Enums.NET/) would be:

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