Make VSCode always capable of providing symbol navigation through *.csproj designated dependencies! #6226
Description
Is your feature request related to a problem? Please describe.
It is not uncommon to have multiple solutions under a single git repository where libraries shared across multiple applications are visible in projects that are referenced by multiple solutions. Dependencies are explicitly referenced from any one project outward to other projects. Solutions encapsulate the build process, not the reference process. Why can't inter project navigation based on symbol definition and references always work?
Describe the solution you would like
The reference mechanisms should always be project based, never solution based. Yes, a symbol may be resolved by a library and a project both. But the normal language resolution mechanisms via using statements dictate exactly where multiple definitions should be resolved into a single desired symbol.
Applicable Scenarios
Anytime there are multiple solution files in a single project, that might create confusion about what "run" means or what "build" output should result when building a "directory tree" visible inside of visual studio code. But, that should be okay. All other IDEs I've used in other languages have always, first provided working symbol based navigation and searching that always worked. Running, building, debugging etc. limitations/requirements and other project kinds of things should never interfere with simple navigation aids.
Describe alternatives you've considered
You could just provide visual studio and stop trying to recreate it with code...