StreamReader Constructor (String, Encoding)


The .NET API Reference documentation has a new home. Visit the .NET API Browser on to see the new experience.

Initializes a new instance of the StreamReader class for the specified file name, with the specified character encoding.

Namespace:   System.IO
Assembly:  mscorlib (in mscorlib.dll)

new : 
        path:string *
        encoding:Encoding -> StreamReader


Type: System.String

The complete file path to be read.

Type: System.Text.Encoding

The character encoding to use.

Exception Condition

path is an empty string ("").


path or encoding is null.


The file cannot be found.


The specified path is invalid, such as being on an unmapped drive.


path includes an incorrect or invalid syntax for file name, directory name, or volume label.

This constructor initializes the encoding as specified by the encoding parameter, and the internal buffer size to 1024 bytes. The StreamReader object attempts to detect the encoding by looking at the first three bytes of the stream. It automatically recognizes UTF-8, little-endian Unicode, and big-endian Unicode text if the file starts with the appropriate byte order marks. Otherwise, the user-provided encoding is used. See the Encoding.GetPreamble method for more information.

The path parameter can be a file name, including a file on a Universal Naming Convention (UNC) share.

The path parameter is not required to be a file stored on disk; it can be any part of a system that supports access using streams.


When you compile a set of characters with a particular cultural setting and retrieve those same characters with a different cultural setting, the characters might not be interpretable, and could cause an exception to be thrown.

For a list of common I/O tasks, see Common I-O Tasks.

The following code example demonstrates this StreamReader constructor.

No code example is currently available or this language may not be supported.

.NET Framework
Available since 1.1
Available since 2.0
Windows Phone Silverlight
Available since 7.0
Return to top