{"id":11461,"date":"2016-01-20T11:22:00","date_gmt":"2016-01-20T19:22:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2016\/01\/20\/introducing-the-windows-powershell-ise-preview\/"},"modified":"2019-02-18T12:38:23","modified_gmt":"2019-02-18T19:38:23","slug":"introducing-the-windows-powershell-ise-preview","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/introducing-the-windows-powershell-ise-preview\/","title":{"rendered":"Introducing the Windows PowerShell ISE Preview"},"content":{"rendered":"<p>Today I&#8217;m pleased to share some exciting new plans that will change how we develop the PowerShell ISE so that it keeps up with the evolving needs of our users. &nbsp;Those of you who saw the teaser at the end of the announcement of <a title=\"PowerShell support for Visual Studio Code\" href=\"http:\/\/blogs.msdn.com\/b\/powershell\/archive\/2015\/11\/17\/announcing-windows-powershell-for-visual-studio-code-and-more.aspx\">PowerShell for Visual Studio Code<\/a>, this is the follow-up you&#8217;ve been patiently waiting for!<\/p>\n<p>Here are the details:<\/p>\n<h2>A new preview release model for the PowerShell ISE<\/h2>\n<p>The biggest news is that we&#8217;ve developed a new strategy to <strong>ship a separate preview edition of the PowerShell ISE.<\/strong>&nbsp;This enables us to add new features and release them to all of you much faster than before. &nbsp;Previously you had to wait for new Windows or WMF releases before you would get an updated ISE. &nbsp;Thanks to the <a title=\"PowerShell Gallery\" href=\"https:\/\/www.powershellgallery.com\">PowerShell Gallery<\/a>, we can now ship the Windows PowerShell ISE Preview as often as we like!<\/p>\n<h3>How does this affect the built-in PowerShell ISE?<\/h3>\n<p>One useful aspect of this release model is that you can use both the built-in PowerShell ISE and the ISE Preview on the same machine at the same time. &nbsp;This allows you to try out new ISE Preview features without disrupting any mission-critical work or demos that rely on the stable built-in release. &nbsp;Eventually some of the new features shipped in the ISE Preview will appear in a future version of the built-in PowerShell ISE in Windows. &nbsp;Our goal is to quickly iterate on new improvements in the ISE Preview with the help of early adopters so that we know we&#8217;re making the right changes before we integrate them back into the built-in ISE.<\/p>\n<h3>Installing the ISE Preview<\/h3>\n<p>Installing the ISE Preview is easy! &nbsp;To install it system-wide, use this command in an elevated PowerShell prompt:<\/p>\n<p><span style=\"font-family: 'courier new', courier\">Install-Module -Name PowerShellISE-preview<\/span><\/p>\n<p>You can also use the&nbsp;<span><span style=\"font-family: 'courier new', courier\">-Scope CurrentUser<\/span> parameter if you&#8217;d like to install it only for your account.<\/span><\/p>\n<p>Once the module is installed, you can launch the ISE Preview with the following alias:<\/p>\n<p><span style=\"font-family: 'courier new', courier\">isep<\/span><\/p>\n<p>If you&#8217;d like to have Start Menu shortcuts created, you can use the following command:<\/p>\n<p><span style=\"font-family: 'courier new', courier\">Install-ISEPreviewShortcuts<\/span><\/p>\n<p>These new shortcuts will launch the new ISE Preview directly out of its installed module path.<\/p>\n<p><em>NOTE: If these commands are not found, you might need to run <span style=\"font-family: 'courier new', courier\">Import-Module PowerShellISE-preview<\/span> first.<\/em><br \/>&nbsp;<\/p>\n<h3>Current Limitations<\/h3>\n<ul>\n<li>Currently the ISE Preview <strong>only works with PowerShell v5 installed<\/strong>, either in-box with Windows 10 (RTM and November Update) or with WMF 5.0 Production Preview.<\/li>\n<li>This preview release is English-only. &nbsp;We want to be able to add new UI without involving the localization team until the new changes have stabilized.<\/li>\n<li>Existing add-ons could have issues running in the new ISE Preview. &nbsp;We&#8217;ve tested a couple of popular add-ons (ISE Steroids, Azure Automation Authoring Toolkit) and things generally seem fine. &nbsp;Please feel free to send us feedback if you see add-on issues that only appear in the ISE Preview.<br \/>&nbsp;<\/li>\n<\/ul>\n<h2>A new plan for PowerShell ISE feature development<\/h2>\n<p>You may notice after installing the ISE Preview that not much has changed; this is intentional! &nbsp;This first release is meant to ensure that the new preview release model will work and that there are no major issues. &nbsp;After the initial release, we hope to ship a new release roughly once per month with new feature improvements and bug fixes. &nbsp;It will also be a lot easier to ship minor releases to address bugs that may appear due to new features.<\/p>\n<p>Here are some improvement areas where we&#8217;ll be investing effort:<\/p>\n<h3>Add-on model improvements<\/h3>\n<p>The biggest area of investment will be improvements to the add-on model to make it easier for add-on authors to implement useful new features. &nbsp;I&#8217;d also like to experiment with the addition of new official features which are developed as open-source add-ons from day one. &nbsp;This will allow the community to get directly involved in the development of these new features.<\/p>\n<p>The ultimate goal of these add-on improvements is to enable all non-core feature additions to be developed and updated independently of the core PowerShell ISE codebase. &nbsp;This will allow the core ISE experience to remain minimal while easily being able to bring in powerful new tools developed both by Microsoft and the PowerShell community. &nbsp;<\/p>\n<h3>Addressing UserVoice feedback<\/h3>\n<p>The other big area of investment will be to work on high-value improvements that address user feedback. &nbsp;Now that we have an easy way to release new updates to the PowerShell ISE, we&#8217;d like to start tackling the &nbsp;issues that have been filed on our UserVoice site. After this initial release, we&#8217;ll start chipping away at this backlog of feature requests prioritized by the number of votes each has received. &nbsp;Please go check out the&nbsp;<a title=\"ISE and Tooling\" href=\"https:\/\/windowsserver.uservoice.com\/forums\/301869-powershell\/category\/148050-ise-and-tooling\">ISE and Tooling<\/a>&nbsp;section of the&nbsp;<a title=\"PowerShell UserVoice site\" href=\"https:\/\/windowsserver.uservoice.com\/forums\/301869-powershell\">PowerShell UserVoice site<\/a>&nbsp;and go vote up all of the feedback items that you&#8217;d like to see us work on!<br \/>&nbsp;<\/p>\n<h2>Let us know what you think!<\/h2>\n<p>We&#8217;re excited to hear what you think of this plan and the initial PowerShell ISE Preview release. &nbsp;Please let us know in the comments section below!<\/p>\n<p>&nbsp;<\/p>\n<p><span>David Wilson (<\/span><a title=\"@daviwil\" href=\"https:\/\/twitter.com\/daviwil\">@daviwil<\/a>)<br \/><span>Senior Software Engineer<\/span><br \/><span>Windows PowerShell Team<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Today I&#8217;m pleased to share some exciting new plans that will change how we develop the PowerShell ISE so that it keeps up with the evolving needs of our users. &nbsp;Those of you who saw the teaser at the end of the announcement of PowerShell for Visual Studio Code, this is the follow-up you&#8217;ve been [&hellip;]<\/p>\n","protected":false},"author":611,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-11461","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":"<p>Today I&#8217;m pleased to share some exciting new plans that will change how we develop the PowerShell ISE so that it keeps up with the evolving needs of our users. &nbsp;Those of you who saw the teaser at the end of the announcement of PowerShell for Visual Studio Code, this is the follow-up you&#8217;ve been [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/11461","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/611"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=11461"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/11461\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=11461"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=11461"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=11461"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}