Fix extension startup on Linux/macOS with PS 6 Alpha 18

daviwil · daviwil · commit 1fbd1c1467c2 · 2017-04-07T14:31:15.000-07:00
This change fixes an issue caused by PowerShell 6 Alpha 18 where the PSModulePath casing on UNIX systems has been changed from PSMODULEPATH back to PSModulePath. This change broke the startup script that manipulates the PSModulePath so the extension fails to load in the new version. This is a breaking change for those using a previous version of PowerShell 6 on UNIX systems. Fixes #662.
diff --git a/scripts/Start-EditorServices.ps1 b/scripts/Start-EditorServices.ps1
@@ -181,7 +181,7 @@ function Get-AvailablePort {
 
 # Add BundledModulesPath to $env:PSModulePath
 if ($BundledModulesPath) {
-    $env:PSMODULEPATH = $env:PSMODULEPATH + [System.IO.Path]::PathSeparator + $BundledModulesPath
+    $env:PSModulePath = $env:PSModulePath + [System.IO.Path]::PathSeparator + $BundledModulesPath
 }
 
 # Check if PowerShellGet module is available

Original file line number	Diff line number	Diff line change
`@@ -181,7 +181,7 @@ function Get-AvailablePort {`
`181`	`181`
`182`	`182`	`# Add BundledModulesPath to $env:PSModulePath`
`183`	`183`	`if ($BundledModulesPath) {`
`184`		`- $env:PSMODULEPATH = $env:PSMODULEPATH + [System.IO.Path]::PathSeparator + $BundledModulesPath`
	`184`	`+ $env:PSModulePath = $env:PSModulePath + [System.IO.Path]::PathSeparator + $BundledModulesPath`
`185`	`185`	`}`
`186`	`186`
`187`	`187`	`# Check if PowerShellGet module is available`