-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
F# IntelliSense is completely broken in specific project (DocFX) #4446
Comments
It looks like the language service is not initialized for this project. Nor does ordering work in the project system. The authoring of the project is a bit odd, with a shared props file doing something I'm unfamiliar with:
Additionally, running
The project in question doesn't reference this, but it's still odd. @KevinRansom @TIHan any ideas? |
|
Last few Visual Studio versions I've been getting the same error in F#: Previously, I use to be able to walk up to any third-party F# method and "Go To Definition" and get some kind of decompiled F# list of methods like I did this with my F# FAKE scripts, now I get this crazy error box. 😢 "Go To Definition" works as long as your "going to" methods defined inside your project. 😢 |
LOL. Some 6 months later, I finally found what was causing "Cannot navigate to the symbol under the caret." error. See: #4016 Basically, if you have forward slashes in your F# FAKE scripts:
You'll get this error. Change the
and now F12 (Go to Definition) works!!!!!!! This caret 🥕 error was driving me absolutely insane. |
Fixed by #7376 |
Steps to reproduce:
git clone --branch fsharp_extract https://github.com/surban/docfx.git
Open All.sln within the cloned repository with VIsual Studio 2017 (15.5 or 15.6 preview).
Build the solution with the default settings. It should restore NuGet packages and build without issues.
Open the file "FSharpCompilation.fs" within the project "Microsoft.DocAsCode.Metadata.ManagedReference.FSharp" using the solution explorer.
Expected result:
IntelliSense and functions like "Go to Definition" are working.
Actual result:
IntelliSense does not work at all and "Go to Definition" on any symbol results in the message "Cannot navigate to the symbol under the caret.".
This issue has been moved from https://developercommunity.visualstudio.com/content/problem/200003/f-intellisense-is-completely-broken-in-specific-pr.html
VSTS ticketId: 569025
These are the original issue comments:
(no comments)
These are the original issue solutions:
(no solutions)
The text was updated successfully, but these errors were encountered: