Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialRanvir Sahota
9,844 PointsWhy 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
231,198 PointsIt 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
9,844 PointsRanvir Sahota
9,844 Pointshttps://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
231,198 PointsSteven Parker
231,198 PointsI wasn't able to try it out, but what about this, starting at line 16:
If that's not it, please show the complete error message.