WindowsCompatibility
WindowsCompatibility copied to clipboard
PowerShell
Module that allows Windows PowerShell Modules to be used from PSCore6
Using the IIS WebAdministration module with WIndowsCompatibilty does not load the IIS: provider. into a PowerShell 7 session. To reproduce: 1. Install Web-Server 2. Using WInCompat: Load-WinModule -Name WebAdminstration 3....
There seems to be an issue when attempting to import the module as a part of a users profile. In my profile I determine which version of PowerShell I'm using...
If I try to install the docker package I get an error, even using WInCompat: ```powershell PS C:\Foo> Install-package -Name Docker -ProviderName DOckerMSFTProvider -Force Install-package : The term 'Get-WindowsFeature' is...
The best practices module, a standard module in WIndows can not be loaded by PowerShell 7 as it's not based (yet) on .NET Core. However, it also does not load...
Using WIndows Server 2019 1903 and PowerShell Core 6.2.1 Cannot load the ADDSDeploymeht module which means I cannot use the Install-ADDSForest and other cmdlets from that module. If I try...
I create PSDrives to use in my daily sessions, like having an S: drive that points to C:\Scripts. I can then use the built-in function S: to change locations. Works...
There is nothing stopping PowerShell core of installing a module that requires the full .net framework. For example, I've developed this [WcfPS](https://github.com/Sarafian/WcfPS) and within it I do heavy use of...
This is a great module, however it still requires scripts to be "rewritten" that have import-module natively in them. I propose adding a command Register-WinImportModule, that will add a proxy...
This is done to not trigger unnecessary module loads during command auto-discovery.
Metadata
Owner
Metadata
Module that allows Windows PowerShell Modules to be used from PSCore6