WindowsCompatibility icon indicating copy to clipboard operation
WindowsCompatibility copied to clipboard

Module that allows Windows PowerShell Modules to be used from PSCore6

Results 33 WindowsCompatibility issues
Sort by recently updated
recently updated
newest added

This is a little hard to explain and I'm not sure if this is a PowerShell Core issue or something with WindowsCompatibility. So I have some transcripts to explain. Each...

Fix #64 Each execution of the `Import-WinModule` adds **.WinModule** to the name of the imported module if the module is from NeverClobberList. This PR adds check if the name already...

When we call, for example ```powershell Import-WinModule Microsoft.PowerShell.Management ``` there will be **Microsoft.PowerShell.Management.WinModule** module ```powershell Get-Module Microsoft.PowerShell.Management* ModuleType Version Name ExportedCommands ---------- ------- ---- ---------------- Manifest 6.1.0.0 Microsoft.PowerShell.Management {Add-Content, Clear-Content,...

There is code in the module like this: # Location Changed handler that keeps the compatibility session PWD in sync with the parent PWD # This only applies on localhost....

`Add-WindowsPSModulePath` adds empty entries if any of the environment variables contain empty strings like `path;;path` or `[System.Environment]::GetEnvironmentVariable('PSModulePath', [System.EnvironmentVariableTarget]::User)` is null or empty. After running `Add-WindowsPSModulePath`: ``` 4143> $Env:PSModulePath -split [System.IO.Path]::PathSeparator...

bug

I was able to install WindowsCompatibility 1.0 RC1 in my Linux PS 6.1 environment. My idea was to PS Remote into a Windows machine to execute a Module there. As...

enhancement

Each of the cmdlets should accept a `-PSSession`. Currently the parameters for `Initialize-WinSession` only create a WSMan connection. Should support any PSSession type.

enhancement

The changes I've made are to allow the module to run in PowerShell core 6.1 on non-Windows OSes - the original code wasn't designed to connect to an SSH session....

Variables are not passed to *Filter* parameter on any cmdlet from *ActiveDirectory* module imported through *Import-WinModule*: ![variables](https://user-images.githubusercontent.com/16168755/43769101-44a2aeac-9a39-11e8-970a-9f14d92716ae.jpg) **Workaround:** Use string formatting operator

Looking to figure out what the root cause is for this so that I can anticipate problems with other modules. ```powershell PS C:\Users\zeroadmin> Import-WinModule NTFSSecurity Import-Module : Failed to generate...