Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

C# C# Streams and Data Processing Reading Data Console I/O

Ranvir Sahota
Ranvir Sahota
9,844 Points

Why use Console.SetIn(reader)?

Why use (option 1) Console.SetIn(reader) Console.WriteLine(Console.ReadLine()) instead of (option 2) Console.WrtieLine(reader.Reader.ReadLine())

What are the benefits to using option 1 over 2. 1 creates more lines and forces you to have to convert Console back to its standard input. By the how is that done? I tried OpenStandardInput but that still throws an error: System.ObjectDisposedException

1 Answer

Steven Parker
Steven Parker
218,654 Points

It sounds like something being done of out order.

Your exception type makes it seem like you are trying to work with an object after it has been disposed. Perhaps your code needs to be moved into a using block?

You might need to show more of the code to make analysis possible.

Ranvir Sahota
Ranvir Sahota
9,844 Points

https://pastebin.com/mdzaFgjK It also does not throw anymore errors but still, won't return to the normal standard input. I appreciate the help

Steven Parker
Steven Parker
218,654 Points

I wasn't able to try it out, but what about this, starting at line 16:

            foreach (var line in fileLines) {
                using (var reader = new StreamReader(fileName))
                {
                  Console.SetIn(reader);
                  Console.WriteLine(Console.ReadLine());
                }
            }

If that's not it, please show the complete error message.