10 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Kent Boogaart commented  ·  May 14, 2013 3:35 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Think some peeps are misunderstanding, or perhaps I am. The point is not to allow the execution of a PS script as part of a build event, but to enable editing of PS scripts with full syntax highlighting/Intellisense/debugging et cetera. Currently one must download a separate tool to do this, and I completely agree that this should all be in VS. At worst, a separate flavor of VS.

• Daver commented  ·  September 7, 2012 11:34 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Yes, it needs to be fully supported in VS Studio like C#.

• metadings commented  ·  May 6, 2012 1:15 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Consider: Your current object browser view, or your current project bindings class view, interactive and scriptable...

• metadings commented  ·  May 5, 2012 3:26 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Visual Studio: Interactive PowerShell'ing IDE !

  please bring back dimgray borders and white background !!!

• tugberk commented  ·  March 2, 2012 1:13 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  You can still run powershell commands on Project Build Events. Here is how I do that:

  powershell -file "$(SolutionDir)tools\pack.ps1" $(SolutionDir) $(ProjectPath)

  But I agree that it would be great to have OOB support for this.

• Anthony commented  ·  February 29, 2012 9:25 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I don't even use this feature and still voted for it. Powershell should be everywhere. However, you could just put your powershell build script in your project (for quick editing), and set the pre/post build event to call that script (i.e. powershell.exe $(ProjectDir)\postbuild.ps1) right?

• Jeremie Chassaing commented  ·  February 25, 2012 8:12 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Sorry, my phone sent this one without my consent...
  The point is to better integrate powershell as an automation mean in VS, to go further that what is possible today with the package manager console of NuGet.
  Provide better console,
  Add better automation than raw DTE com interface.
  Use it more widely in the whole ide.

• Michael Paterson commented  ·  January 27, 2012 4:58 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I would totally vote for this too if I hadn't already used them all. Great idea.

• AdminVisual Studio UV Site Admin (Admin, Microsoft) commented  ·  January 23, 2012 6:28 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @jeffpierson - I added a vote for you, just don't tell anyone ;-)

  Doug Turnure
  Visual Studio PM

• jeffpierson commented  ·  January 3, 2012 4:35 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I would vote on this but all my votes are used up.