JetBrains Rider Fails to Resolve .cshtml Symbols in Specific Git Branches

Below are some ideas and steps you can try to troubleshoot and resolve the issue:

1. Clear ReSharper Caches

Even though you’ve already invalidated Rider’s caches, try clearing ReSharper’s caches specifically. In Rider go to:

• Tools > ReSharper > Options (or use the ReSharper menu in your solution)
• Look for an option like "Clear Caches" or "Suspend/Resume" ReSharper and then resume it.

  This forces ReSharper to reindex the solution and can sometimes resolve stale state issues introduced by branch changes.

2. Compare Project Files and Settings

Since the issue is branch-specific, it’s possible that the Git Patch changed some project or solution configuration files. Compare the branch with issues against the initial branch (where everything is working) to see if there are discrepancies in:

• Project (.csproj) files
• Solution (.sln) files
• ReSharper configuration files (like DotSettings)

Even a minor change in target frameworks, missing references, or altered project settings can cause ReSharper to lose track of symbols.

3. Force a Full Rebuild and Package Restore

Sometimes dependencies can get out of sync in a particular branch. Try the following steps:

SHELLCopied
# From the command line in your solution directory:

# For a .NET solution
dotnet restore
dotnet clean
dotnet build

The above ensures that all packages are restored and projects are rebuilt from scratch. After doing this, let Rider reindex the solution automatically.

4. Disable and Re-enable ReSharper

Occasionally toggling ReSharper off and then on again in Rider can force a full reindex:

• Go to File > Settings > Plugins
• Find ReSharper, disable it (restart Rider), then re-enable it and restart Rider again.

5. Verify Git Patch Effects

Since you mentioned the issue started after applying a Git patch, double-check what was patched. It might have inadvertently modified:

• References in project files
• Global assembly settings
• Other configuration files that ReSharper relies on for symbol resolution

Even if the changes look innocuous, rolling them back temporarily (or comparing with a backup) can help isolate the issue.

6. Reevaluate the Branch Differences

Check if:

• Any folder/file used in Rider settings was accidentally renamed or moved.
• There are any lingering differences in how the solutions are loaded:
  • Verify the affected branch’s startup project is set up correctly.
  • Ensure that all dependencies (NuGet and project references) are correctly resolved in Rider’s project view.

Final Thoughts

Because Visual Studio (without ReSharper) resolves symbols correctly in the same branch, the core project configuration is likely intact. This points toward ReSharper’s internal indexing or configuration being affected—possibly by changes your Git Patch introduced. Following the above steps should help you reset ReSharper’s state and uncover any underlying configuration differences in your project files.

If none of these steps help, consider reaching out to the JetBrains Rider support team with detailed branch diffs and log files. This may help identify if it’s an edge-case bug within Rider 2024.3.5.