Automating the world one-liner at a time…
Efran Cobisi has published a PowerShell V2 book in Italian. The title is “Windows PowerShell 2.0 – Guida completa” and is a 448 pages long. Efran describes it as “a collection of theory, insides and hints on the scripting environment, the programming language and the most used cmdlets. It’s targeted to both developers and IT professionals and contains many sections devoted to help people with previous experiences "with other shells (CMD, COMMAND.COM, BASH, KSH, CSH, ...) as well.”
If you can read Italian, you can find out more about it HERE.
Sadly I don’t read Italian but I’ve visited Rome a number of times and fell in love with the sound of the language. As such, I’m going to wait for the audiobook.
Jeffrey Snover [MSFT] Distinguished Engineer Visit the Windows PowerShell Team blog at: <a href="http://blogs.msdn.com/PowerShell">http://blogs.msdn.com/PowerShell</a> Visit the Windows PowerShell ScriptCenter at: <a href="http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx">http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx</a>
I have a question about C# calls Powershell. Is there any limitation or disadvantage? Basically we have application which is powershell cmdlet. However I'd like to automation them. We are debating between using invoke directly with create a class wrap the cmdlet. So I'd like to know that is there any disadvantage of create a wrapper class of cmdlet. From my perspective I felt that creating a wrapper added up overhead of calling cmdlet directly. So any idea or recommendation would be great? Thanks