{"id":226115,"date":"2019-08-20T08:00:33","date_gmt":"2019-08-20T15:00:33","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=226115"},"modified":"2019-08-19T14:06:14","modified_gmt":"2019-08-19T21:06:14","slug":"the-powershell-you-know-and-love-now-with-a-side-of-visual-studio","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/the-powershell-you-know-and-love-now-with-a-side-of-visual-studio\/","title":{"rendered":"The PowerShell you know and love now with a side of Visual Studio"},"content":{"rendered":"<p>While we know that many of you enjoy, and rely on the Visual Studio Command Prompt, some of you told us that you <a href=\"https:\/\/twitter.com\/shanselman\/status\/953749597620457472\">would prefer to have a PowerShell<\/a> version of the tool. We are happy to share that in Visual Studio 2019 version 16.2, we added a new Developer PowerShell!<\/p>\n<h2>Using the new Developer PowerShell<\/h2>\n<p>We also added two new menu entries, providing quick access to not just the <strong>Developer PowerShell,<\/strong> but also for the <strong>Developer Command Prompt<\/strong>. These menu entries are located under <strong>Tools<\/strong> &gt; <strong>Command Line<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"alignnone wp-image-226140\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/c-users-rurios-appdata-local-microsoft-windows-in-6.jpeg\" alt=\"C:\\Users\\rurios\\AppData\\Local\\Microsoft\\Windows\\INetCache\\Content.MSO\\7DF5E1ED.tmp\" width=\"700\" height=\"489\" srcset=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/c-users-rurios-appdata-local-microsoft-windows-in-6.jpeg 800w, https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/c-users-rurios-appdata-local-microsoft-windows-in-6-300x210.jpeg 300w, https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/c-users-rurios-appdata-local-microsoft-windows-in-6-768x537.jpeg 768w\" sizes=\"(max-width: 700px) 100vw, 700px\" \/><\/p>\n<p>Also, you can access the Developer Command Prompt and Developer PowerShell via the search (Ctrl +Q):<\/p>\n<p><img decoding=\"async\" class=\"alignnone wp-image-226143\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/word-image-15.png\" alt=\"\" width=\"650\" height=\"189\" srcset=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/word-image-15.png 550w, https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/word-image-15-300x87.png 300w\" sizes=\"(max-width: 650px) 100vw, 650px\" \/><\/p>\n<p>Selecting either of these tools, will launch them in their respective external windows, and with all the predefined goodness (e.g. preset PATHs and environment variables) you already rely on.<\/p>\n<p>Opening them from Visual Studio automatically adjust their directories based on current solution or folder\u2019s location. Additionally, If no solution or folder is open at the time of invocation, their directories are set based on the \u201cProjects location\u201d setting. This setting is located under <strong>Tools &gt; Options &gt; Locations<\/strong>.<\/p>\n<p><img decoding=\"async\" width=\"1772\" height=\"550\" class=\"wp-image-226144\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/word-image-16.png\" srcset=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/word-image-16.png 1772w, https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/word-image-16-300x93.png 300w, https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/word-image-16-768x238.png 768w, https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/08\/word-image-16-1024x318.png 1024w\" sizes=\"(max-width: 1772px) 100vw, 1772px\" \/><\/p>\n<h2><\/h2>\n<h2><\/h2>\n<h2>Try it out and let us know what you think!<\/h2>\n<p>We\u2019d love to know how it fits your workflow. Please reach out if you have any suggestions or comments around how we could further improve the experience. Send us your feedback via the <a href=\"https:\/\/developercommunity.visualstudio.com\/spaces\/8\/index.html\">Developer Community<\/a> portal or via the <strong>Help &gt; Send Feedback<\/strong> feature inside Visual Studio.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>While we know that many of you enjoy, and rely on the Visual Studio Command Prompt, some of you told us that you would prefer to have a PowerShell version of the tool. We are happy to share that in Visual Studio 2019 version 16.2, we added a new Developer PowerShell! Using the new Developer [&hellip;]<\/p>\n","protected":false},"author":1092,"featured_media":226181,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1085,1388,155,1029],"tags":[354,4237,4236,526],"class_list":["post-226115","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cloud","category-extensibility","category-visual-studio","category-web","tag-announcement","tag-developer-command-prompt","tag-powershell","tag-productivity"],"acf":[],"blog_post_summary":"<p>While we know that many of you enjoy, and rely on the Visual Studio Command Prompt, some of you told us that you would prefer to have a PowerShell version of the tool. We are happy to share that in Visual Studio 2019 version 16.2, we added a new Developer PowerShell! Using the new Developer [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/226115","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/1092"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=226115"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/226115\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/226181"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=226115"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=226115"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=226115"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}