Uh-Oh. Work has many cmd scripts in use. They'll all have to be tested under PS now.
No, batch files won't magically get run by PowerShell (and in fact cannot, except for very trivial stuff).
Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
61–70 of 350 posts
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#62Weird. I have 14971 installed and when I type CMD in the "ask me anything" box or in the alt-r box I get good old CMD shell. Is this a config thing ?
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#63Btw did anyone noticed that in windows 10 you can resize cmd.exe to more than 80 characters width! When I first saw it I almost cried.
Seriously? I wonder how they managed to do that, i am sure that required a whole engineer team for a whole month!
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#64So basically instead of doing dir C:\ I have to learn to type List-Directory-With-Files Drive=C Folder=/ (made up example, but you get the point)
At least Powershell has Unixy aliases for the common commands. I don't know how many times I've been in a cmd shell and typed ls and then swore at things.
I just wrote batch files that serve as aliases for those. I type ls in my command shell and it does a dir /w behind the scenes, which makes it look more like how it looks in Linux anyway. Here are the ones I have:
* cat.bat: type %1
* clear.bat: cls
* diff.bat: fc /n /w %1 %2
* ls.bat: dir /w %1%
* pwd.bat: cd
* touch.bat: echo . >> %1
* top.bat: tasklist
All have an @echo off at the top too. Touch is a little janky, because I couldn't figure out how to actually create an empty file with nothing in it from the command prompt.
I'm actually not really a Linux person, but on Mac you kinda have to use these, so I got more used to using them than the Windows counterparts.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#65Btw did anyone noticed that in windows 10 you can resize cmd.exe to more than 80 characters width! When I first saw it I almost cried.
I've been able to do that in versions of Windows going back as far as I can remember.
Correct me if i am wrong, but all i remember is you could edit the width somewhere in the options. But there was no way to change the width _on the fly_ (assuming thats something it does now)
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#66Why ? Because some linux zealots think it's the best option ? Laughable.
Hey, I'm still on Windows desktop after having tried Linux desktop more times than I can count. But to claim that bash (or most other shells) are only preferable to cmd and powershell if you're a linux zealot is what is truly laughable.
If you have ever worked with both there would be no question.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#67Weird. I have 14971 installed and when I type CMD in the "ask me anything" box or in the alt-r box I get good old CMD shell. Is this a config thing ?
They're not removing cmd the console host. If you shift-right-click a folder the context item is powershell now instead of command prompt.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#68Btw did anyone noticed that in windows 10 you can resize cmd.exe to more than 80 characters width! When I first saw it I almost cried.
Seriously? I wonder how they managed to do that, i am sure that required a whole engineer team for a whole month!
https://technet.microsoft.com/en-us/library/dn167709.aspx
> Every idea for a feature starts out with an imaginary deficit of -100 points. That means it has to demonstrate a significant net-positive effect on the product as a whole in order to emerge as being truly worthy of consideration.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#69Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#70Just another reason to stay away from Windows as a platform. Windows 10 is a moving target if you are trying to work with it.
If you're not a fan of change, I feel like software development probably isn't the right career choice.
In technology, there's points where certain things stabilize and change infrequently. You can only build great things when your foundation isn't changing all the time.
I'm not really a heavy shell programmer. I mostly use it for git and simple scripts.
IMO, nothing's really "sold" me on powershell. It's always come across as some tool that some people like, but I've never really seen a reason to use it. (As I don't do a lot of complicated things in the shell.)
Hopefully this is something that's easy to get used to.