Skip to content
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

ProjectReferences in csproj break intellisense #1457

Closed
lewislabs opened this issue May 5, 2017 · 7 comments
Closed

ProjectReferences in csproj break intellisense #1457

lewislabs opened this issue May 5, 2017 · 7 comments

Comments

@lewislabs
Copy link

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.1)

Product Information:
 Version:            1.0.1
 Commit SHA-1 hash:  005db40cd1

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\1.0.1```
VS Code version:
1.12.1
C# Extension version:
1.9.0
## Steps to reproduce
Adding a project based reference to a .csproj e.g.
```xml
<ItemGroup>
       <ProjectReference Include="..\MyOtherProject\MyOtherProject.csproj" />
</ItemGroup>

Expected behavior

Omnisharp can handle <ProjectReference> the same way it can handle <PackageReference>.

Actual behavior

Adding the reference results in omnisharp not being able to recognise any namespaces or types from the referenced project. And intellisense doesn't work as expected.

@lewislabs
Copy link
Author

This could be the same problem as described in #371

@lewislabs
Copy link
Author

and #963

@DustinCampbell
Copy link
Member

It's not #371, but it sounds to me like the same issue as #963, which is already fixed for the next release. Would you be willing to try the latest beta release and let us know if it works better for you? The release is available here. Be sure to follow the instructions at Installing Beta Releases.

@lewislabs
Copy link
Author

I'll give it a go and let you know. If it fixes the problem I will be very happy!

@markushauge
Copy link

Had the same problem, and the beta release fixed it!

@lewislabs
Copy link
Author

Thanks @DustinCampbell, that's worked perfectly for me!

@DustinCampbell
Copy link
Member

Glad to hear it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants