IntelliSense of C# does not respect (upper-/lower) case

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:It bothers me. A fix would be nice]
As you can see on the print screen below, IntelliSense does not prioritize the correct casing of a word and therefore often suggesting the wrong word - when completing the word with tab, one has to go back and correct the case.

Expected behavior: The correct case has a higher priority, still upper- and lower-case versions should be suggested, but if I start with a lower-case and there are words that start with lower-case they should come first in the list and the upper-case ones after (and vice-versa).

In the example above, the typed word does not match any of the available words using an ordinal comparison, but as "chartd" matches "chartDefinition" better than "ChartDefinition" (one case violation against two case violations), "chartDefinition" should be suggested top followed by "ChartDefinition", "LoadChartDefinition" and "LoadChartDefinitions".

---

Original Comments

Feedback Bot on 12/15/2025, 08:44 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Nur Umairah binti Hakimi (Centific Technologies Inc) [MSFT] on 12/19/2025, 00:25 PM:

Thanks for your sharing the steps, I can reproduce this issue, and this issue has been escalated for further investigation, if there is any process, I will inform you immediately.

Feedback Bot on 2/17/2026, 04:42 AM:

This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.

[deepakrathore33]

Repro steps

1. Open Visual Studio.
2. Create a new C# Console App.
3. Replace Program.cs with the code below.
4. In Main, start typing chartd.
5. Press Tab to accept IntelliSense.

Actual: ChartDefinition is often selected first.
Expected: chartDefinition should be ranked first because casing matches better.

using System;

namespace IntelliSenseCaseRepro
{
    class ChartDefinition
    {
    }

    class Program
    {
        static void Main(string[] args)
        {
            ChartDefinition chartDefinition = new ChartDefinition();

            // Type: chartd
        }
    }
}

[MihuBot]

I'm a bot. Here are possible related and/or duplicate issues (I may be wrong):

• Intellisense not ordering by casing #39764
• Surprising completion selection in Roslyn test #24540

[CyrusNajmabadi]

In the all lowercase search string case, there is a lack of information indicating that lowercase is preferred. It's used a lot to match all sorts of different casings. I do not believe it appropriate to presume that something which doesn't match in casing, but had less casing mismatches is better.