.NET types doesn't work in many cases.

[savpek]

Heres example how intellisense fails to support .net types.

First working version and then modified failing one.

vscode: 1.0
extension: 0.5.0

[daviwil]

Hmm, will investigate this, thanks for reporting!

[rkeithhill]

As a workaround for the NewGuid case, try this: type[System.Guid] and then press Ctrl+Space. You should see this:

This will work a little better in 0.6.0 however @daviwil we currently do not provide parameter/arg Intellisense for .NET methods like we do for PowerShell commands AFAICT e.g.:

That would be really nice to have for .NET methods where you show various method overloads e.g. 1/6 instead of command parameter sets.

[daviwil]

That's true, we don't yet provide parameter hints for .NET methods. I was looking for the signature string in the IntelliSense but it seems you just need to get to it a different way, as shown by your screenshot.

One thing that surprised me was that [System. doesn't get a completion list.

[daviwil]

Looks like the completion problems you were having are fixed in 0.6.0 which is releasing soon. I'll close this bug as soon as that is released.

We're tracking the lack of .NET method signature help here: PowerShell/PowerShellEditorServices#13. I'm going to start working on that in the next couple of releases since it will be a great productivity boost.

[daviwil]

0.6.0 is now released! Let me know if you run into any further trouble.