{"id":2131,"date":"2013-04-05T12:56:00","date_gmt":"2013-04-05T12:56:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2013\/04\/05\/microsoft-script-explorer-next-steps\/"},"modified":"2019-02-18T13:05:33","modified_gmt":"2019-02-18T20:05:33","slug":"microsoft-script-explorer-next-steps","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/microsoft-script-explorer-next-steps\/","title":{"rendered":"Microsoft Script Explorer: Next Steps"},"content":{"rendered":"<p>For those who are familiar with Microsoft Script Explorer for Windows PowerShell, you know that we haven&#8217;t released additional updates to it since we published the release candidate (RC) in August 2012. Over the past few months, we have been talking with customers and partners and taking a hard look at the adoption rate of the RC in terms of the number of downloads and the feedback we&#8217;re received to date.<\/p>\n<p>One of the results of this analysis was that the adoption and usage of the pre-release versions of Script Explorer were not at the level we had hoped. Part of this stems from the fact that customers already have a number of options in the market for discovering and sharing PowerShell scripts, and most appear content to continue using these existing mechanisms. As a result, we&#8217;ve decided not to bring the Script Explorer project to RTM.<\/p>\n<p>In the meantime, we will start winding down the Script Explorer project. This will be a gradual process to allow time for existing users to move to other tools. We&#8217;ll start by removing the RC package from the Download Center this week.<\/p>\n<p>For those who have already downloaded pre-release versions and are actively using Script Explorer in their environments, we will continue to operate the back-end script aggregation service used by Script Explorer for a few more months. We plan to turn off the service on June 14, 2013.<\/p>\n<p>To help with migrating from Script Explorer to other solutions, we would like to highlight a few of the existing options that you might find useful for discovering and sharing PowerShell scripts:<\/p>\n<p><a href=\"http:\/\/technet.microsoft.com\/en-us\/scriptcenter\/\">TechNet Script Center<\/a><\/p>\n<p><a href=\"http:\/\/poshcode.org\/\">PowerShell Code Repository<\/a><\/p>\n<p><a href=\"http:\/\/powershell.com\/\">PowerShell.com<\/a><\/p>\n<p><a href=\"http:\/\/powershell.org\/\">PowerShell.org<\/a><\/p>\n<p><a href=\"http:\/\/www.bing.com\/\">Bing<\/a><\/p>\n<p><a href=\"http:\/\/www.idera.com\/Free-Tools\/PowerShell-Plus\/\">PowerShell Plus<\/a> and <a href=\"http:\/\/www.idera.com\/Free-Tools\/PowerShell-scripts\/\">PowerShell Scripts<\/a> by Idera<\/p>\n<p><a href=\"http:\/\/www.powergui.org\/\">PowerGUI<\/a> by Quest<\/p>\n<p><a href=\"http:\/\/www.sapien.com\/software\/powershell_studio\">PowerShell Studio<\/a>&nbsp;by SAPIEN<\/p>\n<p><a href=\"http:\/\/code.msdn.microsoft.com\/\">Microsoft Developer Network<\/a><\/p>\n<p><a href=\"http:\/\/www.codeplex.com\/\">CodePlex<\/a><\/p>\n<p>And there are lots of others. Feel free to add your favorites in the comments below.<\/p>\n<p>Thanks,<\/p>\n<p>The PowerShell Team<\/p>\n","protected":false},"excerpt":{"rendered":"<p>For those who are familiar with Microsoft Script Explorer for Windows PowerShell, you know that we haven&#8217;t released additional updates to it since we published the release candidate (RC) in August 2012. Over the past few months, we have been talking with customers and partners and taking a hard look at the adoption rate of [&hellip;]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[248],"class_list":["post-2131","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell","tag-powershell"],"acf":[],"blog_post_summary":"<p>For those who are familiar with Microsoft Script Explorer for Windows PowerShell, you know that we haven&#8217;t released additional updates to it since we published the release candidate (RC) in August 2012. Over the past few months, we have been talking with customers and partners and taking a hard look at the adoption rate of [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/2131","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\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=2131"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/2131\/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=2131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=2131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=2131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}