PowerShell and .NET version number alignment ? #19982
Replies: 2 comments 2 replies
-
Depends on how we think of PowerShell. If we think of it as integral to dotnet as something like ASP.NET, then it should follow similar versioning. Since PowerShell is pinned to the .NET lifecycle, it would make sense to align things so that similar messaging about support lifecycle, etc. can be communicated simply via the version number. If we see it as its own standalone application, then reserving major version changes for large breaking changes or indicating major improvements seems reasonable outside the .NET ecosystem. As I recall the PS team views it as the latter. |
Beta Was this translation helpful? Give feedback.
-
Agree with Justin, after so many iterations of .NET, the new additions aren't that relevant any more to the majority of PS users who do not use webserver features, it's mostly just perf improvements. |
Beta Was this translation helpful? Give feedback.
-
There is the possibility of aligning the version numbers of PowerShell and .NET on next November with the next Stable release of .NET and PowerShell.
However this is not the direction the PowerShell team has chosen.
I do not understand this choice, so I launch this discussion and this vote to see the opinion of the community.
31 votes ·
Beta Was this translation helpful? Give feedback.
All reactions