VSCode Intellisense for CSX not showing doc for types other than CSX references

[ZurielCorrea]

Create a CSX file in VSCode.

Scenario 1: (fixed for .NET Core, not fixed for Desktop .NET)

• Type "System.IO.", Expected result: intellisense shows the xml doc descriptions for the types and member types.
  Actual result: intellisense won't show the xml docs.

Scenario 2: (fixed)

• Create a simple assembly with a type that has xml docs in the classes and members.
• Add a #r ".dll" to the CSX file, (may require restarting omnisharp or even restarting vscode to make intellisense recognize the new reference) Expected result: intellisense shows the xml doc descriptions for the types and member types.
  Actual result: intellisense won't show the xml docs.

Scenario 3: (not an issue)

• Create a CSX file called file1.csx and add a public method with a summary xml doc.
• Reference "file1.csx" in another csx file using #load.
• Type the name of the method from file1.csx Expected result: intellisense shows the xml doc description
  This one works as expected.

[filipw]

@Zuriel-C thanks, I created https://github.com/OmniSharp/omnisharp-roslyn/pull/686 to (mostly) fix it

Add a #r ".dll" to the CSX file, (may require restarting omnisharp or even restarting vscode to make intellisense recognize the new reference)

Correct, these references are not processed in real time yet. ctrl+shift+p/cmd+shift+p and then restart omnisharp will be enough to get it picked up. The plan is to have it react in real time in the future though.

[filipw]

Scenario 2 has been fixed. Scenario 1 has been fixed for .NET Core but not for desktop CLR where references to mscorlib and System.Core are implicit.

[filipw]

Correct, these references are not processed in real time yet. ctrl+shift+p/cmd+shift+p and then restart omnisharp will be enough to get it picked up. The plan is to have it react in real time in the future though.

This is now part of OmniSharp.