3 ms·
Powershell Core 6.0 wasn't fully backwards compatible. I imagine that full backwards compatibility would be a requirement to replace 5.1. It looks like Powersh
by jamesgeck0 7y ago
Powershell Core 6.0 wasn't fully backwards compatible. I imagine that full backwards compatibility would be a requirement to replace 5.1.
It looks like Powershell 7 still can't run some 5.1 scripts. Here's a compatibility table:
https://docs.microsoft.com/en-us/powershell/scripting/whats-new/cmdlet-versions?view=powershell-7 https://docs.microsoft.com/en-us/powershell/scripting/whats-...
- TheGoddessInari 7y agoThey changed the default path outout of applets like get-childitem. Microsoft employees stated that this would break many older scripts, but it wasn't listed as a breaking change. It's unlikely to ever reach even generally acceptable levels of compatibility with the built-in version.