Quote:
this current solution takes 31 minutes and 44 seconds to read the entirety of the CSV file.
As far as I understand, the problem is not reading the csv, the problem is what you do with it.
Show a sample CVS with 2 rows and what should go in datasetTable.
With a csv like:
title1,t2,t3,t4
a,b,c,d
e,f,g,h
I expect your code to fill datasetTable like:
datasetTable[0,0]="a";
datasetTable[0,1]="ab";
datasetTable[0,2]="abc";
datasetTable[1,0]="abcde";
datasetTable[1,1]="abcdef";
datasetTable[1,2]="abcdefg";
Which is probably not what you want.
Your code do not behave the way you expect, or you don't understand why !
There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your code is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.
Debugger - Wikipedia, the free encyclopedia[
^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[
^]
Basic Debugging with Visual Studio 2010 - YouTube[
^]
Debugging C# Code in Visual Studio - YouTube[
^]
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.