XOR said:I generally dont search my csv files - I generally parse the entire file for
an import or something.
But basically what I do is load the file into a StringReader and then split
each line by the delimited to get each individual cell.
eg:
reader = new StreamReader( FileUploadImport.PostedFile.InputStream);
while (reader.Peek() >= 0) //not eof
{
String line = reader.ReadLine();
String[] items = line.Split(',');
//now you can get the cells
String name = items[0];
}
Vincy said:you can reference Interop.Excel Com object and use
oXL.Workbooks.OpenText
where oXL is the Excel.Application.
you can loop through the Usedrange to get the no. of rows and columns used.
You have Cells.Offset or Cell.Select to get the individual cell.
Regards,
Vincent
XOR said:I generally dont search my csv files - I generally parse the entire file for
an import or something.
But basically what I do is load the file into a StringReader and then split
each line by the delimited to get each individual cell.
eg:
reader = new StreamReader( FileUploadImport.PostedFile.InputStream);
while (reader.Peek() >= 0) //not eof
{
String line = reader.ReadLine();
String[] items = line.Split(',');
//now you can get the cells
String name = items[0];
}
you can reference Interop.Excel Com object and use
oXL.Workbooks.OpenText
where oXL is the Excel.Application.
you can loop through the Usedrange to get the no. of rows and columns used.
You have Cells.Offset or Cell.Select to get the individual cell.
Regards,
Vincent
XOR said:I generally dont search my csv files - I generally parse the entire file for
an import or something.
But basically what I do is load the file into a StringReader and then split
each line by the delimited to get each individual cell.
eg:
reader = new StreamReader( FileUploadImport.PostedFile.InputStream);
while (reader.Peek() >= 0) //not eof
{
String line = reader.ReadLine();
String[] items = line.Split(',');
//now you can get the cells
String name = items[0];
}
Otis said:you can reference Interop.Excel Com object and use
oXL.Workbooks.OpenText
where oXL is the Excel.Application.
you can loop through the Usedrange to get the no. of rows and columns used.
You have Cells.Offset or Cell.Select to get the individual cell.
Regards,
Vincent
XOR said:I generally dont search my csv files - I generally parse the entire file for
an import or something.
But basically what I do is load the file into a StringReader and then split
each line by the delimited to get each individual cell.
eg:
reader = new StreamReader( FileUploadImport.PostedFile.InputStream);
while (reader.Peek() >= 0) //not eof
{
String line = reader.ReadLine();
String[] items = line.Split(',');
//now you can get the cells
String name = items[0];
}
However, as revealed in your previous post where you ask how to use a semicolon
for a delimiter, you lose the ability to tailor the reading of the file(s) to
your specifications.
It is better to write the parsing code yourself unless you are OK with the
defaults of some ready made solution.
Parsing delimited files as XOR has shown you, is not at all difficult at all,
and is something every developer should learn to do proficiently .
Good luck with your project,
Otis Mukinfus
http://www.arltex.com
http://www.tomchilders.com
I agree with the general statement, but anybody who thinks that
parsing CSV (specifically) is trivial hasn't read the full CSV spec...
in the *full* case, since it has disparate escape sequences for
different scenarios (such as quoted and unquoted, multiline, etc) it
can be just painful. And don't forget that some internationalisations
of CSV apps use semicolon instead of comma by default (Excel in French
IIRC). If you know that you only use a subset of the spec then you can
get away with simpler options like Split- and Regex-based solutions.
The codeproject link I posted claims to deal with most scenarios
including choice of delimiter (I'm not vouching for the code, but
looks useful).
Similar to parsing an e-mail address; sounds easy in the
(e-mail address removed) sense, but soon gets scary if you really read
the spec... comments... folding whitespace... uri endpoints (e-mail
addresses without an @), etc...
Marc
Thanks, Mark!It evolved one over time, like fungus. RFC4180 would be a good start:
http://tools.ietf.org/html/rfc4180. But as we are aware, various
implementations over the years lead to all sorts of nuances on this,
including (but not limited to) the semi-colon debacle, line-ending
disparity (note RFC2046 specifies CRLF for all MIME "text" subtypes,
and RFC4180 declares CSV as text/csv, hence CRLF, but LF, CR, and LFCR
should all really be handled for compatibility), and various twists on
quoting.
Marc
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.