PowerShell Team
Automating the world one-liner at a time…
Latest posts
V2 Quick Tip: Starting a new elevated process from a PowerShell script
One of the systems administration hurdles of the post-Vista world is figuring out how to make a script run as an administrator. In PowerShell V2, using the Start-Process cmdlet, this is a one liner that will get the job done: Hope this Helps, James Brundage [MSFT]
Soliciting New Verbs
With the recent changes in v2 to increase the visibility of the cmdlet design guidelines, we want to make sure we have a solid set of verbs on the approved verb list before we ship v2. We've already talked with a number of partners and customers and have made some recent changes to the verb list. In addition, we'd love to have feedback from our community on any holes you perceive we have in our current list of approved verbs. To provide some context, here are the things we think about when deciding whether to add a new verb: When suggesting a new verb, it's most helpful if you can include the following infor...
Do PowerShell Demos in the ISE
Jeffry Snover and many other have used Start-Demo in powershell.exehttp://blogs.msdn.com/powershell/archive/2007/03/03/start-demo-help-doing-demos-using-powershell.aspx Continuing the tradition, we now have ISEDemo.psm1 To use it, start ISE and runImport-Module ISEDemo.psm1 #(attached)Start-Demo c:\path\to\demofile.txt Demo files look like # Get 10 lowest handle count processesgps | sort handles | select -first 10# Import all available modulesGet-Module -ListAvailable | Import-Module Thanks,Ibrahim Abdul Rahim [MSFT]Windows PowerShell TestThis posting is provided “AS IS” with no warranties. ISEDemo.psm1
V2 Quick Tip: Monitoring Performance Counters with PowerShell
I just got a ping on our internal discussion list about how to get at the Performance counters in PowerShell. In V2, we've got some nifty cmdlets to help read performance counters. Here are a few of quick one liners to get you started: Hope this Helps, James Brundage [MSFT]
Adding your own help links to ISE
ISE has an F1 help feature, where if you press F1 when your caret is over a cmdlet name, context sensitive help opens. Shay Levy has a nice post on F1 help in the ISE herehttp://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/01/31/using-help-in-powershell-ise.aspxHe adds “I wanted to mimic the way ISE’s help works when you press F1 and allow an alias to be expanded to cmdlet name.” and he did it with calling hh.exe on the link There is an alternative way; Add your own help links to the ISE You can add to $psLocalHelp and $psOnlineHelp, any key to take you to a help page. For example, $psIse.Options.LocalH...
Script Club In Seattle: Tomorrow Night
If you’re a PowerShell fan, and in the Seattle area, then you should know that Andy Schneider (of Get-PowerShell.com) will be hosting a Script Club event at the Avanade offices. Script Club is a great way to learn PowerShell. Ideally, you bring a laptop, your problems, and your curiosity. Everyone at Script Club helps everyone else get up to speed on PowerShell, answers each others questions, and solves their scripting problems. The first event in Seattle is tomorrow night. Check out this blog post for more details, or register with ClickToAttend, or just show up. The event is from 7pm to 9pm...
Differences between the ISE and PowerShell console
Here is a collection of differences between the PowerShell_ise.exe and PowerShell.exe, as well as workaroundsand suggestion if you need them (assuming we have them :)) There could be others, but parity with PowerShell is a big thing for the ISE. Cheers,Ibrahim Abdul Rahim[MSFT]
15 Minutes with Lang.Net
Microsoft is an awesome place to work on languages! Lang.Net is a great language conference that Microsoft holds every year. We bring in people from all around the industry that are passionate about languages and then race through a set of topics. All the talks are given 15 or 30 minute slots so that we can get through a ton of information. Check out the agenda for this year (HERE) to get a flavor for the wide range of topics and attendees. This year I was given 15 minutes to describe PowerShell! I decided to: You can see the presentation HERE. I would highly recommend w...
Increasing visibility of cmdlet design guidelines
Summary In PowerShell v1, we published a set of cmdlet design guidelines that included direction on how to properly name cmdlets. Throughout the v2 cycle, we've seen an increase in cmdlet authors deviating from the standards in unexpected ways. Our user community (you all) has become particularly vocal in recent months that we needed to do something in v2 to curb this trend. This led to a series of discussions on our team about an appropriate course of action for v2. The outcome of those discussions includes changes to Import-Module where we will perform name checking on imported commands. We decided not to disa...