My Powershell_ISE Profile Part 2

My Powershell_ISE Profile Part 2

  • Comments 6

I messed up.

First let me remind you that what you have are CTP bits and that CTP bits are subject to change.  It turns out that we are tweaking the PowerShell_ISE object model and that the profile I posted does not work with CTP3.  I’m sorry for that screw up.

You can use the amazing PowerShell_ISE to fix this problem.  All you need to do is a search and replace of:

CurrentOpenedRunspace.ToolsMenu

with

CustomMenu

Also GoTo-Line is now built into the editor so you should comment that out.  I’ll keep it in the script (commented out) so that you can see how it works.

I’ve attached the corrected script to this blog.

Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

Attachment: Microsoft.PowerShellISE_Profile.ps1
Leave a Comment
  • Please add 3 and 5 and type the answer here:
  • Post
  • PingBack from http://www.codedstyle.com/my-powershell_ise-profile-part-2/

  • Thanks Jeffrey .. You guys are doing a great Job . The community greatly appreciates these quick responces even during the holidays !!

    Its just awesome !

    Chris

  • Does this mean that the CTP is 'earlier' and more changes are in the wind?

    We were warned!!  :-)

  • > Does this mean that the CTP is 'earlier' and more changes are in the wind?

    Yes.  There is design problem with the CTP3 model.  You can have multiple PSSessions (each one runs your profile) but only 1 toolbar.  Therefore when you run your second PSSession and your profile tries to add a menut item - it fails (noisely) because it is already there.

    Jeffrey Snover [MSFT]

    Windows Management Partner Architect

    Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell

    Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

  • Hello Jeffrey,

    I like ISE very much and meanwhile I updated my main system to V2 CTP 3.

    And I switched form notepadplusplus to using ISE.

    The treatment of multiline commands and commandhistory is just what you need for any script language.

    How specific is ISE to Powershell, it would be nice to use ISE for IronPython or ORACLE ( instead of ISQW).

    Current tools tend to be overloaded. A small extendable thing like ISE is just charming.

    Bernd

    http://pauerschell.blogspot.com/

  • @Bernd

    > How specific is ISE to Powershell, it would be nice to use ISE for IronPython or ORACLE ( instead of ISQW).

    GREAT question!  Currently we only provide syntax coloring for PowerShell and it will probably stay that way for V1.  There is a very small chance that we'll pick up support for XML and C#.  What is going on here is that we are using the same control that Expression Blend is using and the Visual Studio team is using for their next version so we might be able to pick up some syntax support from those teams.  

    Whether than happens for V1 or not, it will certainly happen in the future.  Now you asked about IronPhython.  I've had talks with Jim Hugunin and John Lamm (IronRuby) and we are share a very similar vision of what we want out of an ISE - including the fact that it should be multi-language.  That leads me to be optimistic for the future.  

    Jeffrey Snover [MSFT]

    Windows Management Partner Architect

    Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell

    Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

Page 1 of 1 (6 items)