microsoft / microsoft/vscode-dotnettools

[SUGGESTION] Option For (Go to definition) to Load Source Over DLL Metadata

Open
#474 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-project-cps area-solution enhancement
Dominant language
No language data
Stars
321
Forks
54
Avg merge
2d 19h
Merged PRs (30d)
2

Description

Describe the feature you'd like

tl;dl - Omnisharp's F12 loaded referenced source whereas Language Server Protocol loads DLL's metadata


I work on many projects simultaneously. Some are dependent on others. I've always loved that Omnisharp allowed me to edit dependency source code directly in the dependent project. Unfortunately, LSP loads DLL metadata instead of the original source code, even though I add my projects via <ProjectReference />, not <PackageReference />. Can't say how I truly underappreciated a feature until it's robbed from you.

Now, to edit dependencies, I literally need to spin up another editor specific to that file's project, wait for LSP and everything to load just to get intellisense back, just so I can edit/review as easily as I've done during Omnisharp days.

Alternatives considered

Do what Omnisharp did -- have the editor load up the source file so I can simply make the changes I require.

Environment Information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the F12/Go to definition path and how ProjectReference targets are handled, comparing the current DLL metadata behavior with the OmniSharp behavior described. Done means an option lets users load referenced source files instead of DLL metadata.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.