Familiarity with PowerShell
the fact that Microsoft in the recent past, was delivered of a fresh shell called PowerShell, I have learned more from a year ago. But to try that it for an animal such, in any way hands did not reach. But svejesobranna on Window Server 2008 I found this thing in the composition of the preset component, and curiosity still prevailed. Opened it, tried to fill a couple of commands type "help", "?", etc. in the result, we obtained a list of all commands (in the jargon PowerShella, cmdlets — cmdlets), which turned out quite voluminous. Moreover, the list included names like ForEach, Where, which could not fail to arouse interest in how these designs can touch. I reached for the documentation and was pleasantly surprised to the found translations books-books on the subject (read Windows PowerShell EN) — links can be found on the blog of one of the active participants of the community:
blogs.technet.com/abeshkov/archive/2008/12/24/3172943.aspx
So, after several hours of work with PowerShell in my head was postponed:
— PowerShell is no worse than usual cmd.exe
— I really liked the concept of object-oriented data processing of the commands (cmdlets). Glad that you can go to the branch of the registry, e.g. HKLM as normal disk, with cd HKLM: and wander through it all the same ls and cd, reading the attributes of the registry objects in a manner similar to that used when reading the attributes of files and directories.
I did not like the process of typing long commands and editing them (if they are multi-line). Perhaps in this case it was necessary to work by loading the script files, editing them separately from the shell.
I did not like the syntax PowerShella from the perspective of personal inconvenience — I don't like the fact that you need to precede the name of any variable, the $ sign or the $_ in the case of treatment to the passed object. However, I believe that these inconveniences are quite easy to get used to, but in the code immediately visible variables + minimizing the number of movements.
— I was impressed by the ability to import/export feature to CSV, XML, (as I understand it, this happens through the mechanism of serialization .NET), and especially the ability to interact with COM objects (in the book describes the case where the code in ten lines forms the painted table and stores it in XSLX format).
— Description of the integration of CLS-compliant .NET code PowerShell left a vague impression of a real big achievement in the field of creation of extensible mechanisms administration. (This I did not understand, to wonder how the alleged power of true. However, the fact that you can tie .NET code, in any case, happy).
Overall, the experience is positive and I would be interested in hearing the opinions of those people who work closely with this tool.
Article based on information from habrahabr.ru
blogs.technet.com/abeshkov/archive/2008/12/24/3172943.aspx
So, after several hours of work with PowerShell in my head was postponed:
— PowerShell is no worse than usual cmd.exe
— I really liked the concept of object-oriented data processing of the commands (cmdlets). Glad that you can go to the branch of the registry, e.g. HKLM as normal disk, with cd HKLM: and wander through it all the same ls and cd, reading the attributes of the registry objects in a manner similar to that used when reading the attributes of files and directories.
I did not like the process of typing long commands and editing them (if they are multi-line). Perhaps in this case it was necessary to work by loading the script files, editing them separately from the shell.
I did not like the syntax PowerShella from the perspective of personal inconvenience — I don't like the fact that you need to precede the name of any variable, the $ sign or the $_ in the case of treatment to the passed object. However, I believe that these inconveniences are quite easy to get used to, but in the code immediately visible variables + minimizing the number of movements.
— I was impressed by the ability to import/export feature to CSV, XML, (as I understand it, this happens through the mechanism of serialization .NET), and especially the ability to interact with COM objects (in the book describes the case where the code in ten lines forms the painted table and stores it in XSLX format).
— Description of the integration of CLS-compliant .NET code PowerShell left a vague impression of a real big achievement in the field of creation of extensible mechanisms administration. (This I did not understand, to wonder how the alleged power of true. However, the fact that you can tie .NET code, in any case, happy).
Overall, the experience is positive and I would be interested in hearing the opinions of those people who work closely with this tool.
Comments
Post a Comment