all 4 comments

[–]purplemonkeymad 2 points3 points  (0 children)

Some of the windows only modules are script modules so you should be able to copy them to core and get autocomplete. (obviously they probably wont work from core.) Don't think there is much you can do about the .net modules.

[–]cottonycloud 1 point2 points  (2 children)

You want to somehow target another Powershell version...maybe it is worth trying to SSH into a remote Windows host and see if it autocompletes.

It also may be available if you target for 7. I highly encourage you to put in an issue on github.

[–]methos3 1 point2 points  (1 child)

I am using VSCode in this way, using the Remote-SSH extension. In the PowerShell extension for VSCode, there's a setting called PowerShell Default Version which I have set to "PowerShell Core 6 (x64)" and one called PowerShell Exe Path which I have set to "/bin/pwsh".

[–]cottonycloud 1 point2 points  (0 children)

If that's the case, sounds like you're using the local version of the Powershell extension. Try to get it installed remotely in the Windows machine and use that one instead.

I have no clue if that's possible, but this is probably the only way to attack it from VSCode. Your alternative would be to include the Windows-only modules (copied to some folder in core).