Trying to use PowerShellProTools on VScode getting missing error

[Former user]

Start VSCode load the powershell extension to VSCode run it and get a powershell window install-module PowerShellProTools import-module PowerShellProTools

<shift>-<ctrl><P> to open the menu at the top of the screen and type in: powershell: Show Windows Forms Designer

You get this error message back

command 'powershell.showWinFormDesigner' not found

what did I do wrong please? I was able to successfully license the module

VS Code: Version: 1.30.1 (user setup) Commit: dea8705087adb1b5e5ae1d9123278e178656186a Date: 2018-12-18T18:12:07.165Z Electron: 2.0.12 Chrome: 61.0.3163.100 Node.js: 8.9.3 V8: 6.1.534.41 OS: Windows_NT x64 10.0.17134

$PSVersionTable Name Value ---- ----- PSVersion 5.1.17134.407 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.17134.407 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1

[Adam Driscoll]

Do you have .NET v4.7.2 installed?

You can run this snippet to check:

Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -recurse |
Get-ItemProperty -name Version,Release -EA 0 |
Where { $_.PSChildName -match '^(?![SW])\p{L}'} |
Select PSChildName, Version, Release, @{
  name="Product"
  expression={
      switch -regex ($_.Release) {
        "378389" { [Version]"4.5" }
        "378675|378758" { [Version]"4.5.1" }
        "379893" { [Version]"4.5.2" }
        "393295|393297" { [Version]"4.6" }
        "394254|394271" { [Version]"4.6.1" }
        "394802|394806" { [Version]"4.6.2" }
        "460798|460805" { [Version]"4.7" }
        "461308|461310" { [Version]"4.7.1" }
        "461808|461814" { [Version]"4.7.2" }    
        {$_ -gt 461814} { [Version]"Undocumented version (> 4.7.2), please update script" }
      }
    }
}

[John McCrae]

Oh, interesting. I was running it on OSX. Lemme see.

Cheers John

[Adam Driscoll]

Ah, ok. That's not the issue then. I actually ran into a problem where the extension would not activate in certain circumstances. Might be the problem you are seeing. I will be releasing a new version to fix that in a few days.

[John McCrae]

Adam, I started again on a Windows system and am now getting an error that was cleared up in November? I get the "Cannot load PowerShellPro tools because no valid module file was found....

[Adam Driscoll]

On your windows machine, can you please run the above script to see what version is output?

And I didn't update the extension to fix some issues with activation so you might want to update and try on your OSX machine.

[John McCrae]

You can kill this. I'm stupid. I was trying to import before I installed.

[Adam Driscoll]

All good. Thanks!

[Michael Sumerano]

I'm actually experiencing this on the latest VS Code, latest version of extension, and 4.7.2 is installed on Windows 7.

All I did was install the extension, request a trial license, and then try to use the WinForm designer.

Version: 1.30.2 (system setup)
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:54:13.295Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Windows_NT x64 6.1.7601

PowerShell Pro: 0.7.1

PSChildName Version        Release Product
----------- -------        ------- -------
v2.0.50727  2.0.50727.5420
v3.0        3.0.30729.5420
v3.5        3.5.30729.5420
Client      4.7.03062      461814  4.7.2
Full        4.7.03062      461814  4.7.2
Client      4.0.0.0