Closed JoshClose closed 3 years ago
Looks like this one is also outputting data different:
Group #1 (result JSON length = 921):
- Csv
- CsvHelper
- CsvTextFieldParser
- Ctl_Data
- Cursively
- FastCsvParser
- FluentCsv
- HomeGrown
- LumenWorksCsvReader
- mgholam_fastCSV
- Microsoft_VisualBasic_FileIO_TextFieldParser
- NReco_Csv
- ServiceStack_Text
- string_Split
- SoftCircuits_CsvParser
- Sylvan_Data_Csv
- TinyCsvReader
Group #2 (result JSON length = 939):
- LinqToCsv
Is there a way to test this in your source? I'll make sure they are working with that check before making a pull request.
My approach is to use the Test Explorer in Visual Studio. This will pop up the tests in the solution and you can run them there.
Oh, of course. lol Not sure what I was thinking.
Check encoding.
This library is returning null
for empty strings.
Fixed.
Awesome!
Code is based off of section "Reading Raw Data Rows" https://www.codeproject.com/Articles/25133/LINQ-to-CSV-library#ReadingRawDataRows