-
Notifications
You must be signed in to change notification settings - Fork 676
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
Not getting good intellisense, navigation, etc.. #1196
Comments
Hi, could you try the latest beta of C# for VS Code? This should have much better support for .csproj-based .NET Core projects. Please use our Installing Beta Releases instructions to install the latest beta (currently 1.7.0-beta4). I will take a look at cloning this project and giving it a whirl. But in the short term, please try the beta and let me know if it works any better for you. |
I'll try that right now |
Oh sweet mercy, that's VERY MUCH BETTER! |
I'm very glad to hear that! |
Environment data
VSCode 1.9.0
C# Extension version 1.6.2
Steps to reproduce
I suspect that it's got something to do with the way that I've built my csproj files (it builds/compiles/tests just fine) but I can't seem to get any actual editor awareness of my project
You can see my project/branch: https://github.com/Azure/autorest/tree/coreclr
or clone that branch:
I have some common
.proj
files that I import in the.csproj
files that define common things (like$(SolutionDir)
)In my projects, I reference other projects like this:
where
$(SolutionDir)
was set toand I've also tried this:
Actual behavior
The c# extension reaally hates that. It doesn't give any errors, but I get unresolvable namespaces when I reference projects using
$(SolutionDir)
if I change the all references to relative paths without variables...
I still get the squiggleys. 😞
Hmm.
I even see this in the project that doesn't have any project dependencies (Autorest.Core), so ... not sure why we're seeing :
Those are all references inside that single project.
The OmniSharp Log
output
window:(those exceptions happened when I first typed in a source window)
Expected behavior
I would have hoped that it would be able to give me navigation and intellisense for my project ⛑
This is kindof a blocking issue for us; I can't migrate a bunch of developers over to dotnet-cli & vscode without this working
The text was updated successfully, but these errors were encountered: