http://blogs.technet.com/b/heyscriptingguy/archive/2012/02/09/use-tab-expansion-in-the-powershell-ise-to-avoid-cmdlet-aliases.aspxLearn how to use Tab Expansion in the Windows PowerShell ISE to avoid using cmdlet aliases and to add complete parameter names in commands.en-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/heyscriptingguy/archive/2012/02/09/use-tab-expansion-in-the-powershell-ise-to-avoid-cmdlet-aliases.aspx#3479940Thu, 09 Feb 2012 14:31:47 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3479940Ed Wilson<p>@K_Schulte you are right, it does not seem to work when the command is split. It also seems to break down when I have grouped expressions that when taken together form the value for an argument. But it is very useful, and I wish that Microsoft Word had Tab Expansion as well :-)</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3479940" width="1" height="1">http://blogs.technet.com/b/heyscriptingguy/archive/2012/02/09/use-tab-expansion-in-the-powershell-ise-to-avoid-cmdlet-aliases.aspx#3479866Thu, 09 Feb 2012 09:59:50 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3479866K_Schulte<p>Hi Ed,</p> <p>TAB Expansion is quite helpful and I make often use of it!</p> <p>One thing I&#39;m missing is that it doesn&#39;t work if I split the commandline on different physical lines like</p> <p>Get-Process</p> <p>-co</p> <p>This seems to stop it from working, so I usually have to build a long line and split it later on :-(</p> <p>Klaus (Schulte)</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3479866" width="1" height="1">