{"id":2351,"date":"2012-06-12T18:30:39","date_gmt":"2012-06-12T18:30:39","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2012\/06\/12\/intellisense-in-windows-powershell-ise-3-0\/"},"modified":"2024-02-26T14:29:12","modified_gmt":"2024-02-26T22:29:12","slug":"intellisense-in-windows-powershell-ise-3-0","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/intellisense-in-windows-powershell-ise-3-0\/","title":{"rendered":"Intellisense in Windows PowerShell ISE 3.0"},"content":{"rendered":"

This blog post applies to the Windows PowerShell Integrated Scripting Environment (ISE) in Windows 8 and Windows Server 2012.\u00a0 The ISE is also fully supported and available when Server 2012 is deployed using the Minimal Server Interface<\/a>.\u00a0 To start ISE, type ise<\/strong><\/span>\u00a0 in a PowerShell console and press Enter<\/strong><\/span><\/span><\/em><\/p>\n

Very few things can be considered \u201ccool\u201d in an interactive command-line environment. Intellisense sure counts as one of the few exceptions.\u00a0 While tab completion has always been a cornerstone of PowerShell usability (and continues to be), my struggle with tab completion is that after cycling through the 5th option, I would have already forgotten the first 3 :-).\u00a0 Discoverability is not optimal either, because a user doesn\u2019t always know when tab completion would work, so it becomes a bit of a trial-and-error exercise.\u00a0 Intellisense provides the following added benefits over tab completion:<\/p>\n