Support VS2019 in Import-VisualStudioEnvironment

[tats-u]

Could you support VS2019 in Import-VisualStudioEnvironment?
I can't touch the already-signed code.

PS tatsu@TATSU-NB-3RD:~$ Import-VisualStudioEnvironment
The system cannot find the path specified.
ERROR: Error executing CMD.EXE: 1
PS tatsu@TATSU-NB-3RD:~$ Import-VisualStudioEnvironment 2019
Import-VisualStudioEnvironment : Cannot validate argument on parameter 'VSVersion'. The argume
nt "2019" does not belong to the set "Latest,2013,2015,2017" specified by the ValidateSet attr
ibute. Supply an argument that is in the set and then try the command again.
At line:1 char:32
+ Import-VisualStudioEnvironment 2019
+                                ~~~~
    + CategoryInfo          : InvalidData: (:) [Import-VisualStudioEnvironment], ParameterBin 
   dingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Import-VisualStudioEnvironment 
 
PS tatsu@TATSU-NB-3RD:~$ Import-VisualStudioEnvironment Latest
The system cannot find the path specified.
ERROR: Error executing CMD.EXE: 1

[JohnWintellect]

Unfortunately, I'm not doing active development much anymore these days. If you pull down the code for this repo you can make the fix in there, push me the patch, and I can do the signing.

[tats-u]

I got it. I suppose these changes are needed:

1. Add "2019" in

   WintellectPowerShell/Code/Import-VisualStudioEnvironment.ps1

   Line 69 in 43cdada

   [ValidateSet("Latest", "2013", "2015", "2017")]

2. Add "2019" { "16.0" } in

   WintellectPowerShell/Code/Import-VisualStudioEnvironment.ps1

   Lines 109 to 111 in 43cdada

   	"2013" { "12.0" }
   	"2015" { "14.0" }
   	"2017" { "15.0" }

Similar changes may be required in, e.g.,

• WintellectPowerShell/Code/Remove-IntelliTraceFile.ps1

  Line 54 in 16a335f

  [ValidateSet("VS2013", "VS2015", "VS2017", "Latest")]

• WintellectPowerShell/Code/Remove-IntelliTraceFile.ps1

  Lines 71 to 73 in 16a335f

  	"VS2013" { $regVer = "12.0" }
  	"VS2015" { $regVer = "14.0" }
  	"VS2017" { $regVer = "15.0" }

[tats-u]

Should I create a PR or formal diff file?