dotnet / dotnet/roslyn

Extern aliases not supported for go to definition and find references

Open
#82,176 3 comments 0 reactions 0 assignees View on GitHub
Area-IDE
Dominant language
C#
Stars
20.7k
Forks
4.3k
PR merge metrics
PR metrics pending

Description

## Version Used
VS Community Version 18.2.1
Roslyn 5.0.0-2.26054.2 @ ec501e4c6f2689c9c71e38ce72d892675965c392

## Steps to Reproduce

Assume the project `OtherProject.csproj` that contains the following namespace:
```cs
namespace OtherProject.Core;
```

Linked in `MainProject.csproj` like this:
```xml



```

In our `MainProject` we use `OtherProject` via `extern alias` like this:
```csharp
extern alias Core;

using Core::OtherProject.Core;
```

Place the cursor on any of the occurrences of the **extern alias** `Core` (not the namespace). Invoke either go to definition or find all references.

## Expected Result

Both GTD and FAR work.

## Actual Result

Neither GTD nor FAR work.

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue using OtherProject.csproj and MainProject.csproj with the shown ProjectReference alias and extern alias code. Start by testing Go to Definition and Find All References on the alias occurrence; done means both commands resolve and report references for Core.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.