Automating the world one-liner at a time…
Last year I was delighted to be invited to give a talk at JAOO conference. This is a great language conference. The thing I was delighted to discover is that the while it had Microsoft content (AndersH gave one of the keynotes), the bulk of the people and content was non-Microsoft. This allowed me to give a different kind of a talk. It allowed me to go back to the basics and explain what were were doing and why we were doing it to a group of people that didn't necessarily have any background and were potentially not particularly friendly towards Microsoft. (I've got a funny story about that - ask me in person sometime.)
I hope you enjoy the talk HERE.
Experiment! Enjoy! Engage!
Jeffrey Snover [MSFT] Windows Management Partner Architect Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
As always it's a pleasure to listen to your talks!
Not the place for this, but question:
When I do something like this:
md 1 | cd
I end up with a path like this:
If I do something like this:
cd (md 1)
I end up with a normal path, like this:
I enjoyed the talk and I have been playing with PowerShell for some time now.
I’m a bit disappointed that everything is focused on new functionality instead of fixing what is already in PS.
I mean, in CTP3 it is still impossible to set ACL on files with reserved characters, plz see below.
Has the development team totally forgotten about this issue, or is it just not a priority?
I do not know where to point my attention so I thought I would drop a hint here, maybe someone can direct me somewhere else?
PS C:\Test> Get-Acl 'C:\Test\test.txt'
Path Owner Access
---- ----- ------
test.txt BUILTIN\Administrators BUILTIN\Administrators Allow FullCo...
PS C:\Test> Get-Acl 'C:\Test\test`[0`].txt'
Get-Acl : Cannot find path 'C:\Test\test.txt' because it does not exist.
At line:1 char:8
+ Get-Acl <<<< 'C:\Test\test`[0`].txt'
+ CategoryInfo : ObjectNotFound: (:) [Get-Acl], ItemNotFoundException
+ FullyQualifiedErrorId : GetAcl_PathNotFound,Microsoft.PowerShell.Commands.GetAclCommand
We actually spent a TON of time fixing and filling out things from V1. At some point Kenneth Hansen figured out how to say it well and it became our mantra:
Version 2 should be a better Version 1.
That said, we still had to prioritize and since we are digging our way out of a 30 year hole, it is going to take a while but if you pick up WS08/R2 - I think you'll conclude that things are moving pretty fast.
That doesn't help you if the problem you have isn't getting fixed and I'm sorry about that. We're working as hard and fast as we can.
Experiment! Enjoy! Engage!
Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
Good to hear you are working hard on it.
30 years, maybe that’s bit of a stretch? - I thought Windows/MSDOS history only went back to 1981 and I do not think there were any shells that were better the first 10 years. ;)
Anyway I love PS so much - It certainly is amazing how easy I can do one-liners that would have taken me hours to make in VBS.
Thank you for that.
Hopefully you have fixed the literal paths on Get-ACL/Set-ACL on next CTP *hint* *hint*
Maybe even on all cmdlets, like Rename as well, so we don't have to use Move-item every time ;)