|17.1||Using .NET from PowerShell|
|17.2||PowerShell and the internet|
|17.3||PowerShell and graphical user interfaces|
I love it when a plan comes together!
Col. John “Hannibal” Smith, The A-Team
When we started the design work on PowerShell, our focus was almost exclusively on cmdlets. The plan was to have lots of cmdlets and everything would be done through them. Unfortunately, as Robert Burns observed, “The best laid plans of mice and men often go awry,” and we found that we didn’t have the resources to get all the required cmdlets completed in time. Without these cmdlets, we wouldn’t have adequate coverage for all of our core scenarios. How to solve this, we asked? “Let’s just depend ...