Fixed: Prism commands are very slow in Windows PowerShell on Windows …

…10, Server 2012R2, and Server 2019 due to some overzealous logging.

CHANGELOG.md

@@ -3,6 +3,7 @@
 ## Fixed
 
 * `prism install` fails if `Get-PSRepository` hasn't been run before it.
+* Prism commands are very slow in Windows PowerShell on Windows 10, Server 2012R2, and Server 2019 due to some overzealous logging.
 
 
 # 0.5.0

Prism/Functions/Invoke-Prism.ps1

@@ -51,8 +51,6 @@ function Invoke-Prism
 
         $pkgMgmtPrefs = Get-PackageManagementPreference
 
-        Write-Debug 'AVAILABLE MODULES'
-        Get-Module -ListAvailable | Format-Table -AutoSize | Out-String | Write-Debug
         Import-Module -Name 'PackageManagement' `
                       -MinimumVersion '1.3.2' `
                       -MaximumVersion '1.4.7' `
@@ -65,11 +63,6 @@ function Invoke-Prism
                       -Global `
                       -ErrorAction Stop `
                       @pkgMgmtPrefs
-        Write-Debug 'IMPORTED MODULES'
-        Get-Module | Format-Table -AutoSize | Out-String | Write-Debug
-        Write-Debug 'AVAILABLE MODULES'
-        Write-Debug "PSModulePath  $($env:PSModulePath)"
-        Get-Module -ListAvailable | Format-Table -AutoSize | Out-String | Write-Debug
     }
 
     process

appveyor.yml

@@ -14,31 +14,31 @@ environment:
   matrix:
   - job_name: PowerShell 7.2 on Windows
     job_group: pwsh
-    appveyor_build_worker_image: Visual Studio 2022
+    appveyor_build_worker_image: Visual Studio 2022  # Windows Server 2019
 
   - job_name: PowerShell 7.1 on macOS
     job_group: pwsh
     appveyor_build_worker_image: macOS
 
   - job_name: Windows PowerShell 5.1/.NET 4.6.2
     job_group: ps
-    appveyor_build_worker_image: Visual Studio 2013
+    appveyor_build_worker_image: Visual Studio 2013  # Windows Server 2012R2
 
   - job_name: Windows PowerShell 5.1/.NET 4.8
     job_group: ps
-    appveyor_build_worker_image: Visual Studio 2019
+    appveyor_build_worker_image: Visual Studio 2019  # Windows Server 2019
 
   - job_name: PowerShell 6.2 on Windows
     job_group: pwsh
-    appveyor_build_worker_image: Visual Studio 2015
+    appveyor_build_worker_image: Visual Studio 2015  # Windows Server 2012R2
 
   - job_name: PowerShell 7.2 on Ubuntu
     job_group: pwsh
     appveyor_build_worker_image: Ubuntu
 
   - job_name: PowerShell 7.1 on Windows
     job_group: pwsh
-    appveyor_build_worker_image: Visual Studio 2019
+    appveyor_build_worker_image: Visual Studio 2019  # Windows Server 2019
 
 
 artifacts: