Skip to main content

Impress your colleagues with your knowledge about…the TextFieldParser class

Sometimes when working with C# you discover some hidden gems. Some of them very useful, other ones a little bit harder to find a good way to benefit from their functionality. One of those hidden gems that I discovered some days ago is the TextFieldParser class.

This class is well hidden in the Microsoft.VisualBasic namespace – which makes it not very accessible for the C# developer – although there’s nothing VB.NET specific about it. It makes it very easy to process filetypes like CSV and similar formats.

A quick sample:

   1:  using (var csvFile = new TextFieldParser(myFilePath)  
   2:  {   
   3:        csvFile.TextFieldType = FieldType.Delimited;   
   4:        csvFile.SetDelimiters(",");   
   5:        csvFile.CommentTokens = new[] { "HEADER" };  
   6:       
   7:        while (!csvFile.EndOfData)  
   8:        {  
   9:            string[] fieldArray;  
  10:            try  
  11:            {  
  12:                fieldArray = csvFile.ReadFields();  
  13:            }  
  14:            catch (Microsoft.VisualBasic.FileIO.MalformedLineException ex)  
  15:           {  
  16:                // TODO: Handle exception  
  17:                continue;  
  18:            }  
  19:            // TODO: process values in fieldArray  
  20:        }  
  21:   }

Some characteristics of this class:

  • There are several constructor overloads, so you can point it to a file path or a stream or TextReader.
  • TextFieldParser implements IDisposable, so you can use it in a "using" block to automatically close the file or stream when finished.
  • The delimiter value can be specified using the  SetDelimiters method.
  • The CommentTokens property is used to tell TextFieldParser to ignore lines where the text begins with one of the specified strings.
Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more