Skip to main content

How to Resolve Error "CS1026: ) expected" in C#

The Compiler Error CS1026 is a syntax error. The message reads: ") expected".

This is one of the most fundamental parsing errors in C#. It simply means the compiler found an opening parenthesis (, but reached the end of the statement, block, or file without finding the matching closing parenthesis ). This often happens in method calls, if statements, loops, or complex mathematical expressions where parentheses are nested.

This guide helps you spot the missing character and balance your code syntax.

Understanding Parenthesis Balancing​

In C#, parentheses must always come in pairs.

  • Open (: Starts a parameter list, a condition, or a grouping.
  • Close ): Ends that section.

If the compiler encounters a token that signals the start of a new section (like a { or a ;) before it finds the required closing ), it throws CS1026 because the previous structure is incomplete.

Scenario 1: Method Calls and Definitions​

The most common cause is a simple typo where you press the semicolon ; key before pressing the closing parenthesis key.

Example of error​

public class Logger
{
    public static void Log(string message)
    {
        // ⛔️ Error CS1026: ) expected
        // The compiler sees the semicolon and thinks the statement ended, 
        // but the method call was left open.
        Console.WriteLine("System started"; 
    }
}

Solution: Close the Call​

Add the missing parenthesis before the semicolon.

public class Logger
{
    public static void Log(string message)
    {
        // ✅ Correct: Balanced parentheses.
        Console.WriteLine("System started"); 
    }
}

Scenario 2: Control Flow Statements (if, for, while)​

Control flow keywords require their conditions to be wrapped fully in parentheses. This is easy to miss if the condition is long or complex.

Example of error​

Missing the final closing bracket after a condition.

public void CheckAccess(int age, bool hasPass)
{
    // ⛔️ Error CS1026: ) expected
    // We opened two: 'if (' and '(age > 18'.
    // We only closed one.
    if ((age > 18) && hasPass
    {
        Console.WriteLine("Access Granted");
    }
}

Solution: Count Open vs. Closed​

Ensure every ( has a partner.

public void CheckAccess(int age, bool hasPass)
{
    // ✅ Correct: Two opens, two closes.
    if ((age > 18) && hasPass)
    {
        Console.WriteLine("Access Granted");
    }
}
tip

Editor Trick: In Visual Studio or VS Code, place your cursor next to an opening parenthesis. The editor will usually highlight the matching closing parenthesis. If it highlights nothing or the wrong one, you have a mismatch.

Scenario 3: Nested Lambdas and LINQ​

When writing LINQ queries or Lambda expressions, you often end up with a "soup" of parentheses and braces ({ ... }). It is very easy to miss the final closing parenthesis of the outer method call.

Example of error​

We are opening the .Where call, but we never close it after the lambda body.

using System.Collections.Generic;
using System.Linq;

public class Data
{
    public void Filter()
    {
        List<int> numbers = new List<int> { 1, 2, 3 };

        // ⛔️ Error CS1026: ) expected
        // We forgot to close the 'Where' method call.
        var result = numbers.Where(n => n > 1; 
    }
}

Solution: Close the Method​

Ensure the lambda expression ends and the method call also ends.

public class Data
{
    public void Filter()
    {
        List<int> numbers = new List<int> { 1, 2, 3 };

        // ✅ Correct: 'Where( ... )'
        var result = numbers.Where(n => n > 1); 
    }
}

Conclusion​

CS1026 is the compiler asking you to finish what you started.

  1. Check Semicolons: Look immediately to the left of the ; on the error line. Did you forget )?
  2. Check Control Flow: Does your if, while, or for loop have a matching closing bracket?
  3. Count Them: If usage is complex (math equations or LINQ), count the opening ( and ensure there is an equal number of closing ).

Table of Contents