Parsing input to numeric types in C Sharp (C#) - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of parsing valid and invalid numeric strings

What is the output of the following C# code?

C Sharp (C#)

using System;
class Program {
  static void Main() {
    string input1 = "123";
    string input2 = "12.3";
    int result1 = int.Parse(input1);
    try {
      int result2 = int.Parse(input2);
      Console.WriteLine(result2);
    } catch (FormatException) {
      Console.WriteLine("FormatException caught");
    }
    Console.WriteLine(result1);
  }
}

A

123
FormatException caught

B

12
123

C

FormatException caught
123

D

FormatException caught
12

💡 Hint

int.Parse expects a string that represents a whole number without decimals.

The string "123" parses correctly to int 123. The string "12.3" is not a valid integer format, so int.Parse throws a FormatException, which is caught and prints the message. Then the first parsed integer 123 is printed.

❓ Predict Output

intermediate

Parsing float with TryParse and output

What will be the output of this C# code?

C Sharp (C#)

using System;
class Program {
  static void Main() {
    string input = "3.14";
    if (float.TryParse(input, out float value)) {
      Console.WriteLine(value);
    } else {
      Console.WriteLine("Failed to parse");
    }
  }
}

A 3.14

B Failed to parse

C 3,14

D 0

💡 Hint

TryParse returns true if parsing succeeds and outputs the parsed value.

The string "3.14" is a valid float representation in C# when using the invariant culture or default culture with dot decimal separator, so TryParse returns true and prints 3.14.

🔧 Debug

advanced

Why does parsing "-123" to uint fail?

Consider this code snippet: uint number = uint.Parse("-123"); What error will this code produce when run?

A System.OverflowException

B System.FormatException

C System.ArgumentNullException

D No error, number = 4294967173

💡 Hint

uint cannot represent negative numbers.

Parsing "-123" to uint causes an OverflowException because uint only accepts values from 0 to 4,294,967,295. Negative values are out of range.

📝 Syntax

advanced

Identify the syntax error in parsing code

Which option contains a syntax error in parsing a string to int?

A int.TryParse("100", out int result)

B int.Parse("100";

C int.TryParse("100", out result)

D int.Parse("100")

💡 Hint

Check for missing or extra characters in method calls.

Option B is missing a closing parenthesis and semicolon is misplaced, causing a syntax error.

🚀 Application

expert

Result of parsing multiple inputs with culture-specific decimal separator

Given this code snippet: using System; using System.Globalization; class Program { static void Main() { string input1 = "1234,56"; string input2 = "1234.56"; var culture = new CultureInfo("fr-FR"); if (double.TryParse(input1, NumberStyles.Any, culture, out double val1)) { Console.WriteLine(val1); } else { Console.WriteLine("Failed input1"); } if (double.TryParse(input2, NumberStyles.Any, culture, out double val2)) { Console.WriteLine(val2); } else { Console.WriteLine("Failed input2"); } } }

A

Failed input1
Failed input2

B

Failed input1
1234.56

C

1234,56
1234.56

D

1234.56
Failed input2

💡 Hint

The French culture uses comma as decimal separator, not dot.

In "fr-FR" culture, "1234,56" parses correctly as 1234.56 double value. "1234.56" fails because dot is not a valid decimal separator in French culture.

Practice

1.

Which method should you use in C# to convert a string to an integer when you are sure the string contains a valid number?

easy

A. int.TryParse(stringValue, out int result)

B. int.Parse(stringValue)

C. Convert.ToString(stringValue)

D. string.ToInt()

Solution

1. Step 1: Understand the purpose of Parse

   The method int.Parse converts a string directly to an integer if the string is a valid number.

2. Step 2: Compare with TryParse and others

   int.TryParse is used to safely check conversion but requires an out parameter; Convert.ToString converts to string, not number; string.ToInt() does not exist in C#.

3. Final Answer:

   int.Parse(stringValue) -> Option B

4. Quick Check:

   Use Parse when sure input is numeric [OK]

Hint: Use Parse when input is guaranteed numeric [OK]

Common Mistakes:

• Using TryParse without out parameter
• Using Convert.ToString to get a number
• Assuming string.ToInt() exists

2.

Which of the following is the correct syntax to safely convert a string input to an integer using TryParse?

string input = "123";

easy

A. int.TryParse(input, out int result);

B. int.TryParse(input, int result);

C. int result = int.TryParse(input);

D. int result = TryParse(input);

Solution

1. Step 1: Recall TryParse syntax

   TryParse requires the keyword 'out' before the variable to store the parsed value.

2. Step 2: Check each option

   int.TryParse(input, out int result); uses 'out int result' correctly; others miss 'out' or assign TryParse's bool return to int.

3. Final Answer:

   int.TryParse(input, out int result); -> Option A

4. Quick Check:

   TryParse needs 'out' parameter [OK]

Hint: Remember TryParse needs 'out' before result variable [OK]

Common Mistakes:

• Omitting 'out' keyword
• Assigning TryParse result directly to int
• Using invalid method calls

3.

What will be the output of the following C# code?

string input = "456";
if (int.TryParse(input, out int number))
{
    Console.WriteLine(number + 10);
}
else
{
    Console.WriteLine("Invalid input");
}

medium

A. 45610

B. Invalid input

C. 466

D. Compilation error

Solution

1. Step 1: TryParse converts "456" to integer 456

   Since "456" is a valid number, TryParse returns true and sets number = 456.

2. Step 2: Add 10 and print result

   Inside the if block, number + 10 = 456 + 10 = 466, which is printed.

3. Final Answer:

   466 -> Option C

4. Quick Check:

   TryParse success adds 10 to 456 [OK]

Hint: TryParse returns true for valid numbers [OK]

Common Mistakes:

• Thinking TryParse returns the number directly
• Concatenating strings instead of adding numbers
• Assuming else block runs for valid input

4.

Identify the error in the following code snippet that tries to parse a string to an integer:

string input = "abc";
int number = int.Parse(input);
Console.WriteLine(number);

medium

A. No error, code runs fine

B. int.Parse returns 0 for invalid input

C. int.Parse converts "abc" to ASCII values

D. int.Parse throws an exception for non-numeric strings

Solution

1. Step 1: Understand int.Parse behavior

   int.Parse expects a valid numeric string; if input is "abc", it throws a FormatException.

2. Step 2: Check other options

   int.Parse does not return 0 or convert to ASCII; it throws an error, so code will not run fine.

3. Final Answer:

   int.Parse throws an exception for non-numeric strings -> Option D

4. Quick Check:

   Parse throws error on invalid input [OK]

Hint: Parse throws error if input is not numeric [OK]

Common Mistakes:

• Expecting Parse to return 0 on failure
• Ignoring exceptions from Parse
• Confusing Parse with TryParse

5.

You want to read a user input string and convert it to a double safely. Which code snippet correctly handles invalid input without crashing?

string userInput = Console.ReadLine();

hard

A. if (double.TryParse(userInput, out double value)) { Console.WriteLine(value); } else { Console.WriteLine("Invalid number"); }

B. double value = double.Parse(userInput);

C. double value = Convert.ToDouble(userInput);

D. double value = (double)userInput;

Solution

1. Step 1: Understand safe parsing with TryParse

   double.TryParse attempts to convert the string and returns true if successful, avoiding exceptions.

2. Step 2: Check each option for safety

   double value = double.Parse(userInput); and Convert.ToDouble(userInput) throw exceptions on invalid input; double value = (double)userInput; is invalid cast; if (double.TryParse(userInput, out double value)) { Console.WriteLine(value); } else { Console.WriteLine("Invalid number"); } safely checks and handles invalid input.

3. Final Answer:

   if (double.TryParse(userInput, out double value)) { Console.WriteLine(value); } else { Console.WriteLine("Invalid number"); } -> Option A

4. Quick Check:

   TryParse safely converts or handles errors [OK]

Hint: Use TryParse to avoid exceptions on bad input [OK]

Common Mistakes:

• Using Parse without try-catch
• Casting string directly to double
• Assuming Convert.ToDouble never fails