Comments
4 comments
-
Hi John
I am just speaking to the team on this matter.
-
Hi Adam
Exciting; keep me posted. -
Hi Adam Turner - Just hoping to get an update here on this. Would be super excited to have this feature. It's been years since I have requested a new feature. Internally, we're trying to discourage PowerShell 5.1 usage. While it is tied to the Windows OS as a legacy, static component and has no official end-of-life date, we think the right move is to focus on newer technologies with dedicated improvement lifecycles.
-
Actually, according to reddit, it seems as though Windows Server vNext will be the first OS to drop PowerShell 5.1 and move to PowerShell Core. So this is a real product need: https://www.reddit.com/r/PowerShell/comments/1tk06dr/it_seems_that_powershell_7_will_ship_with_windows/
In 2022, Microsoft subtlety shifted the wording on the PowerShell Support Lifecycle page to say that PowerShell is aligned with the underlying operating system. Until now, customers had taken that to mean PowerShell 5.1 would be supported forever :-) - But that appears to be no longer the case.
Add comment
Please sign in to leave a comment.
Hi,
I was wondering if Red Gate could enhance the PowerShellCmdlets.msi to also offer a PowerShellCoreCmdlets.msi - most of the product on the server-side is using .NET Core, and if you look at the PE Header metadata of the assemblies, only RedGate.SqlClone.Client.Api.dll targets .NET Framework 4.7.2 (PowerShell 5.0). Further, it looks like that only depends on System.Net.Http as truly .NET Framework dependency - it doesn't have anything wild like WCF as a dependency. In .NET Core and modern .NET (versions 5 through 9+), the System.Net.Http namespace is fully built-in and included by default as part of the shared framework runtime. You do not need to install a NuGet package to use it.
Thanks,
John