We released a new service build of PowerShell ModuleManger 2023 (v2.0.19), which includes PowerShell 7 support. This service build is included as part of the regular update cycle for our subscribers.
PowerShell 7 Support
Updated Ribbon
Under the ribbon, you can find a new Platform section:
From here, you can toggle between Windows PowerShell and PowerShell 7. This will update the module list for either version based on $PSModulePath.
When checking for updates, the message written to output has been updated to distinguish between Windows PowerShell and PowerShell 7:
We added the PowerShell Version Selector, which lets you easily switch between the PowerShell 7 versions:
An internet connection is required to download the PowerShell installers from GitHub. You can find more information about this tool in Introducing the PowerShell Version Selector – SAPIEN Blog.
The Script Security Center was moved from the Quick Access Toolbar to the new Platform section on the ribbon.
Default PowerShell Setting in Options
Under Options, there is a new setting for the default PowerShell version to be loaded at the start of the application: This can be found under General->PowerShell:
Remoting
Remoting for PowerShell and Windows PowerShell needs to be configured outside of the application.
Switching between Windows PowerShell and PowerShell 7 from the ribbon will affect all tabbed connections as well as the local machine.
Requirements for PowerShell 7 Support
PowerShell 7 will need to be installed before utilizing the functionality mentioned above. PowerShell ModuleManager is built with PowerShell 7.3.4 and runs independently from the version of PowerShell 7 installed. This means it does not require the exact version of PowerShell installed to match the version used to build the application.
New Folder Import Feature
Now you can add folders for PowerShell ModuleManager to locate and import modules. All folders specified will automatically load modules found under the folders.
After adding folders and closing the file menu, the changes will take effect, and the module list will automatically refresh. The application will search for modules under the specified folders, but only up to a depth of 1. This means the application will only search the specified folder and child folders, but will not look further than the child folders. This was done to prevent a major slowdown when checking for module files (.psd1, psm1). Once done refreshing, the modules found will appear in the module list:
Any folder added that includes paths specified in the environmental variable $PSModulePath will be filtered out. These paths can be set for Windows PowerShell and PowerShell 7.
With this import feature, you can now move modules to any import module paths:
There is a warning upon moving modules outside of $PSModulePath:
This functionality is only available for the local machine.
.NET 7 Update
With this release, PowerShell ModuleManager is now a .NET 7 application (previously, it was running on a .NET Framework 4.8). This change alters the application’s dependencies—now, the .NET 7 Desktop runtime will need to be installed. The installer has been updated to reflect this change.
Feedback
Please continue providing your feedback. Many of the new features included in the service builds are suggestions from users like you. Submit your suggestions or feature requests on the Wish List and Feature Requests forum or the new Feature Requests page.
