PowerShell 7 environment integration

All replies

• 

  

  0

  Sign in to vote

  No, it's a completely separate technology. 5.1 is built on .NET Framework whereas 6 or 7 is built on .NET Core.

  Nor is 7 an 'upgrade' to 5.1. There is more functionality that works in 5.1 but does not yet work properly in 7 than the other way around, at least as far as Windows administration is concerned.

  ---

  Evgenij Smirnov

  http://evgenij.smirnov.de

  Friday, June 5, 2020 10:31 PM
• 

  

  0

  Sign in to vote

  There is more functionality that works in 5.1 but does not yet work properly in 7 than the other way around, at least as far as Windows administration is concerned.

  
  
  

  For example?

  Saturday, June 6, 2020 8:03 AM
• 

  

  1

  Sign in to vote

  For example?
  

  Any .NET namespace that isn't in .NET Core, like System.Web. A lot of modules still aren't compatible although it got much better compared to 6. Here's a recent thread: https://twitter.com/adbertram/status/1265344814071111681

  Conversely, I can't think of anything much except SSH remoting and Foreach -Parallel (which you can easily replicate with Runspaces on 5.x) that I'd want to use PS Core on Windows for. Now on Linux, it's a completely different story but that wasn't what you were asking.

  ---

  Evgenij Smirnov

  http://evgenij.smirnov.de

  Saturday, June 6, 2020 8:28 AM
• 

  

  1

  Sign in to vote

  Having said all that, at the PSConfEU earlier this week the PowerShell team made it clear that they are aware of the demand for enterprise deployment options for these products. It is on their roadmap but not as a top priority.

  What we might be seeing in near future though is JEA over SSH - they are actively exploring this but no commitment so far as to when we may be able to lay our hands on a beta.

  ---

  Evgenij Smirnov

  http://evgenij.smirnov.de

  • Marked as answer by N-kei Saturday, June 6, 2020 12:07 PM

  Saturday, June 6, 2020 10:54 AM