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

BCL Intellisense not working #80

Open
mikernet opened this issue Feb 7, 2020 · 8 comments
Open

BCL Intellisense not working #80

mikernet opened this issue Feb 7, 2020 · 8 comments

Comments

@mikernet
Copy link

mikernet commented Feb 7, 2020

BCL Intellisense stops working when the alpha.154 package is added to a .NET Standard 2.1 library.

@jnm2
Copy link
Contributor

jnm2 commented Feb 16, 2020

I saw this as well.

@mikernet
Copy link
Author

Any idea why this could be happening? The path obj\Release\netstandard2.1\annotated contains netstandard.xml so I have no idea what to do to fix this.

@mikernet
Copy link
Author

mikernet commented Mar 17, 2020

It seems to be hit and miss as to which IntelliSense still works and I can't really figure out what the pattern is.

Working examples:

  • Array.Length
  • string.Length
  • string.IsNullOrWhitespace()
  • string.Trim()
  • Comparer<T>.Default

Non-working examples:

  • string.TrimEnd()
  • string.Split()
  • string.SplitAt()
  • Action<T1, T2>.Invoke()

I could be wrong but I think more of the BCL IntelliSense started working after I upgraded to VS 16.5.0...I'm fairly sure the working examples above were not working before.

@jnm2
Copy link
Contributor

jnm2 commented Aug 1, 2020

@mikernet Is this still happening? In VS 16.6.5 I'm getting intellisense for all the above in a project using this in Directory.Build.props:

  <ItemGroup>
    <PackageReference Include="TunnelVisionLabs.ReferenceAssemblyAnnotator" Version="1.0.0-alpha.154" PrivateAssets="all" />
    <PackageDownload Include="Microsoft.NETCore.App.Ref" Version="[3.1.0]" />
  </ItemGroup>

@mikernet
Copy link
Author

mikernet commented Aug 4, 2020

The situation got even worse...not only do I not have intellisense, but I also can't F1 on members to get to docs - it just always goes to https://docs.microsoft.com/en-us/ :/

@mikernet
Copy link
Author

mikernet commented Aug 4, 2020

I think it just so happens that MSDN broke right after I upgraded VS, haha. Bad timing. Intellisense still borked though.

@jnm2
Copy link
Contributor

jnm2 commented Aug 4, 2020

@mikernet Is there a repro project I can look at? It's all working for me in a net472 project with VS 16.6.5, 3.1.0 annotations, and the latest two versions of RAA.

Also did you git clean -xdf since the last time you changed any of these version numbers?

@mikernet
Copy link
Author

mikernet commented Aug 4, 2020

Seems it works for some but not for others. Not working for https://github.com/Singulink/Singulink.IO.FileSystem.

Could be netstandard 2.0 v.s. 2.1?

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

No branches or pull requests

2 participants