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 trial

C# C# Basics (Retired) Perform Converting Strings to Integers

I cant write int with a dot followed after "int" when i try to enter int.Parse("xx")

Whenever I write the dot (.) after "int" in the console it immediately gives me an error and won't allow me to complete the line. It says "Unhandled exceptions" followed by "System.ArgumentException: Cannot be less than one" in the next line, which is then followed by 33 lines of text saying something like "Mono.Terminal.LineEditor.UpdateCompletionWindow......"

To follow up it also exits me out of the repl and back to the regular console

3 Answers

Steven Parker
Steven Parker
228,978 Points

Just to be sure, you're typing this in at the "csharp>" prompt, right? I don't seem to be able to replicate the symptom.

When I type the peroid, I get a little helper box with a list of possible things to put next, starting with "CompareTo". It doesn't exit, even if I type the complete line and get the (expected) error.

This might be an issue to take up with the Support staff.


I've attached a link to a picture showing what happens when I write "int."

I've also highlighted the line where i write "int." (in the picture)

Ill also try to contact support, thank you for the advice. I actually thought this was support :p

Steven Parker
Steven Parker
228,978 Points

Well, this is the place to come for support from other students. But for anything official it's good to contact the staff directly.

Well, this is embarrassing. It works now so i think i just needed to restart the workspace. Thanks for the help anyway :)