r/PowerShell • • Jun 18 '21

Microsoft will release future PowerShell updates via Windows Update

https://www.bleepingcomputer.com/news/microsoft/microsoft-will-release-future-powershell-updates-via-windows-update/
307 Upvotes

93 comments sorted by

View all comments

76

u/allywilson Jun 18 '21 edited Aug 12 '23

Moved to Lemmy (sopuli.xyz) -- mass edited with redact.dev

50

u/EIGRP_OH Jun 18 '21

Seriously? Do they not understand how much more Powershell 7 will be used if they start shipping Windows with it?

26

u/jrdnr_ Jun 18 '21

yes, however I don't believe PS7 was ever intended to be able to fully replace PS5 when it comes to working with Full .Net whatever-they-call-it. So for Windows administration PS5.1 is still required. It sure would make life easier if at least the Azure/M365 teams would be given a mandate to make everything customer facing PS7 support first but not something to hold your breath for.

5

u/[deleted] Jun 19 '21

.Net is a framework btw.

2

u/jrdnr_ Jun 19 '21

Yes, I meant .Net full vs core just couldn't think if there was a name for the closed source version of .Net framework.

0

u/[deleted] Jun 19 '21

[deleted]

3

u/jrdnr_ Jun 19 '21

I get that.

So what is the terminology Microsoft officially uses to differentiate between the closed source (windows only) version vs the current open source version?

To have an intelligent conversation about .Net versions do I need to know and remember version numbers or are there simply names like saying "full" vs "core" that people use to say what they are talking about?

3

u/The_One_X Jun 19 '21

There is Framework, Core, and Standard. You can ignore Standard as it isn't an actual implementation. Framework is the legacy .Net. Core is the modern .Net. Moving forward there will be no new development on .Net Framework the last version is v4.8. After .Net Core 3 Microsoft dropped the name Core, and skipped the number 4 to avoid confusion, so the current version of Core is just .Net 5, and the next version coming out in the fall is .Net 6.

1

u/jrdnr_ Jun 19 '21

That makes sense thanks.

In not general programming terms wouldn't .Net (core) technically be a framework as well?

2

u/Thirdbeat Jun 19 '21

You can have both and use powershell or pwsh as their defined app name. So everything legacy uses powershell, but it's recommended you use pwsh

11

u/Alaknar Jun 18 '21

It's still too young. You have PS 5 on pretty much every Windows server out there, but not necessarily the newer versions of .Net.

And there's quite a bit of incompatibility or behaviour change between 5 and 7.

0

u/[deleted] Jun 18 '21

[deleted]

4

u/DaNPrS Jun 18 '21

Same. I've reverted back to 5.1 as my default shell in VSC.

3

u/da_chicken Jun 19 '21

Nope. The .Net Framework was intentionally designed to tightly integrate with Win32 in some areas specifically to make it difficult to make cross platform. Then mono happened, and then it took off on mobile, and then MS bought Xamarin to buy that platform. They fucked themselves over into owning two incompatible platforms that do the same thing. They vendor locked themselves.

Now they have a bunch of tools that use parts of the .Net Framework that can't be cross platform, and the dev teams for those tools don't want to write the missing libraries. This is the exact same shit that MS did to other companies in the 90s and 00s.

2

u/TheRealMisterd Jun 19 '21

Didn't they killed xamarin's cross platform features before they killed it altogether?

4

u/beth_maloney Jun 19 '21

They've effectively rebranded it. With .net 5 mono now Falls under the .net umbrella. So instead of developing for mono/xamarin you develop for .net and run it on the mono runtime.

mono is still alive and should be considered a complimentary runtime to .net core.

Xamarin supports iOS/Android and they're looking at supporting windows and Mac os X (not sure if that's been released yet).

1

u/The_One_X Jun 19 '21

New versions of .Net are not tied to the OS. They can be installed independently of Windows, so not having them on the machine isn't relevant.

1

u/Alaknar Jun 19 '21

So what? It still means you have to install it on all those old systems or risk compatibility issues if someone unaware wrights the script in PS7 and deploys it to an unsupported server.

1

u/The_One_X Jun 20 '21

It means when you install PS7 it will also install the necessary dependencies at the same time. You don't have to worry about if the right version of .Net is installed.

0

u/Alaknar Jun 20 '21

You're missing the point.

It still requires installing stuff on existing servers. There are companies that have thousands of those, and you can't just throw a deployment to SCCM to all machines and call it a day, there's a change process for that, testing period to ensure everything remains stable. There's always the risk of BSODing something, so you can't quickly install it on mission critical boxes if you don't have proper redundancy. Etc., etc.

There's A LOT of work needed to push something like that to your whole environment, so Microsoft not replacing PS 5 with 7 us doing the sensible thing.