PowerShell, the new command line interface
This doesn’t bode well. This Dotnet thing is snowballing for me. Now Microsoft has come up with the next generation of the command line shell, called: PowerShell Batch.
Now I have to spend time picking this up. Being a command line person, it’s kind of a given. It’s a huge, kind of complicated, but very powerful replacement of DOS and CMD.exe .
The link above is an excellent introduction to what it can do for you , and it gives you the most important command examples, so that you can at least start using it for the primary usages of the command line that are common among many users.
Where this ties in with DOTNET:
Everything is based on objects with this PowerShell. You can iterate through a structure, for example, that was in itself returned from a previous command, and save results into objects, and then read a value via object properties. In fact, some or all of the commands return .Net objects, such as the DateTime type. So the more you know about the dotnet framework, the more power you can get out of it.
A quote from the article, and my last sentence in this entry, since I need some java right about now.
The .NET framework is the foundation on which PowerShell runs. The more you know about .NET, the better your PowerShell experience will be.