New
#1
Thanks for the heads up Brink
PowerShell 7.1.0 RC1 released
- [Regression] The console API System.Console.TreatControlCAsInput is backwards on Linux and macOS: dotnet/runtime#42423. The fix was made in .NET 5.0.0-rc.2: dotnet/runtime#42432
- This causes the Ctrl+c to not work in PSReadLine on Linux and macOS.
- [Regression] The console API System.Console.ReadKey() incorrectly returns Ctrl+J for ENTER on macOS: dotnet/runtime#42418. The fix was made in .NET 5.0.0-rc.2: dotnet/runtime#42477
- This causes ENTER to not be functional in the PSES integrated console.
- [Regression] Performance regression on Linux and macOS: dotnet/runtime#41739. The fix was made in .NET 5.0.0-rc.2: dotnet/runtime#41820
- This causes potential performance issues on some specific architectures, Linux distros, and macOS. For instance, the command discovery in PowerShell is up to 20x slower on Ubuntu 18.04 WSL 2.
- [By-design breaking change] TLS 1.0 and TLS 1.1 were retired from the default on Linux machines where OpenSSL 1.1 and above is used: dotnet/runtime#40746
- This causes Invoke-WebRequest and Invoke-RestMethod to throw AuthenticationException when using TLS 1.0 or TLS 1.1 on Linux machines where OpenSSL 1.1 and above is used.
- Make fixes to ComInterop code as suggested by .NET team (#13533)
- Fix case where exception message contains just "`n" on Windows (#13684)
- Recognize CONOUT$ and CONIN$ as reserved device names (#13508) (Thanks @davidreis97!)
- Fix ConciseView for interactive advanced function when writing error (#13623)
-
-
-
New #3
Hi Brink , thanks for the direct information. I have the version 5.1.
Do you know which is the latest version, which is 100% compatible with version 5.1, cause I thinking of installing it if it exists ?
-
New #4
You could install the latest official release of PowerShell 7 instead of the previews if wanted.
How to Install PowerShell 7.0 in Windows 7, Windows 8, and Windows 10
-
New #5
Thanks. I think a find an answer : "Improved compatibility with existing Windows PowerShell modules".
- - - Updated - - -
And the question now is : why i need to have the 5.1 version alongside with 7.0 , if they are 100% compatible ?You could install the latest official release of PowerShell 7 instead of the previews if wanted.
How to Install PowerShell 7.0 in Windows 7, Windows 8, and Windows 10
-
New #6
It looks like the article you linked to explains all of it for them to run side by side for now.Thanks. I think a find an answer : "Improved compatibility with existing Windows PowerShell modules".
- - - Updated - - -
And the question now is : why i need to have the 5.1 version alongside with 7.0 , if they are 100% compatible ?
-
New #7
-
-
-
New #9
I thought that PowerShell 7 could be downloaded from the store so I did. Then I read that some 5.0 Runtime should have been installed. So I removed the one from the Store and Downloaded PowerShell 7.1.1 RC1 from Git hub and installed it using .MSI. When I had an earlt version the Icon was different , not it looks just like PS 7. Could that be because it is a Release Candidate?
PowerShell 7.1.0 RC1 released
Posted: 30 Sep 2020
Known Issues
This release of PowerShell is impacted by a few known regressions and a by-design breaking change in .NET 5.0.0-rc.1.
Given the impact of these regressions, particularly in interactive scenarios on non-Windows systems, we will only be publishing PowerShell v7.1.0-rc.1 packages for Windows and Linux, skipping macOS until v7.1.0-rc.2 is available with the proper fixes.
Engine Updates and Fixes
General Cmdlet Updates and Fixes
Read more: https://github.com/PowerShell/PowerShell/releases/
Quote
Related Discussions
