{"id":15368,"date":"2018-07-16T06:00:24","date_gmt":"2018-07-16T13:00:24","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=15368"},"modified":"2018-07-13T13:26:46","modified_gmt":"2018-07-13T20:26:46","slug":"sapien-technologies-on-windows-powershell-and-powershell-core","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2018\/07\/16\/sapien-technologies-on-windows-powershell-and-powershell-core\/","title":{"rendered":"SAPIEN Technologies on Windows PowerShell and PowerShell Core"},"content":{"rendered":"

SAPIEN Technologie’s PrimalScript<\/em>™ and PowerShell Studio<\/em>™ products have always supported Windows PowerShell. With the Generally Available (GA) release of the open source PowerShell Core, we began the integration and support of this new technology into our products.<\/p>\n

The chart below shows the differences between the Windows PowerShell and PowerShell Core products:<\/p>\n

\"\"<\/a><\/p>\n

We use this as our guide to support both technologies.<\/p>\n

Unique Editor<\/h3>\n

The editors in our SAPIEN products stand on their own and do not follow the same model of other editors. It is not practical to compare a lightweight<\/em>\u00a0editor with a rapid application development<\/em>\u00a0editor, and we are not suggesting to stop using other editors\u2014they all have their unique purpose and can complement each other in many ways.<\/p>\n

We are continuing to integrate PowerShell Core in our\u00a0PrimalScript<\/em> and\u00a0PowerShell Studio<\/em> editors\u2014two powerful tools developed to help you be more productive.<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

We will continue to update and improve these tools as PowerShell Core evolves.<\/p>\n

What about Window PowerShell?<\/h3>\n

Microsoft has stated that Windows PowerShell is “complete”\u2014this does not mean that it is obsolete, nor will it be deprecated anytime soon. Microsoft has invested a lot in this technology, and it is not being relegated to the trash bin.<\/p>\n

Another chapter has opened for PowerShell\u2014all future efforts and improvements will be towards PowerShell Core. There are no plans for another version of Windows PowerShell, as there will be “no feature development.”<\/p>\n

Check out Jeffreys Snover’s video “State of the Art<\/a>” about the state of Windows PowerShell.<\/p>\n

There will be Windows PowerShell security fixes and customer “blocking” bug fixes only. Report any Windows PowerShell issues in the Windows PowerShell UserVoice<\/a> forum, and report PowerShell Core issues on Github<\/a>.<\/p>\n

The last version of Windows PowerShell is 5.1.<\/p>\n

Summary<\/h3>\n

As PowerShell Core keeps evolving our development team will make the necessary changes to our products, and we will also continue to support Windows PowerShell.<\/p>\n

Most importantly we value your suggestions and feedback, which help our products be the best in this industry.<\/p>\n

References<\/h3>\n