Replacing cmd.exe

re: Replacing cmd.exe

Pablo — Wed, 31 Oct 2007 23:47:51 GMT

Sorry but i can't agree with you, also because you can run on powershell also the commands you are usual to do with cmd.

I think powershell is the answer a lot of sysadmins had expected for too much time, because even if a gui program is more friendly to use, nothing can replace the powerfull of a text-based command-line (and cmd.exe is not usefull for this kind of works).

My compliments for your blog.

re: Replacing cmd.exe

Robert Toups — Mon, 21 May 2007 22:39:36 GMT

Do have a link to a press release stating that VBScript is heading to the dustbin of history? Just curious. I missed that one.

re: Replacing cmd.exe

Aaron Margosis — Mon, 21 May 2007 05:47:23 GMT

@me: Perhaps I'm misunderstanding what you're trying to say, but console applications do not invoke cmd.exe. Invoking a BAT or CMD script will load cmd.exe to run in, but EXE files do not. If you invoke a console app (e.g., netsh.exe) from the Run dialog, it will display in a console window, but that's not cmd.exe.

re: Replacing cmd.exe

me — Sun, 20 May 2007 03:02:35 GMT

My main problem with cmd.exe is that it is the default when loading console applications. Due to its historical origins, it has almost no support for Unicode I/O. Console applications are going to be around for a lot longer, but they will never get full Unicode support like a modern Windows application.

While I have the option of configuring which application to load for a text document, console applications are executed in cmd.exe by default and I can not change this. This is a serious problem. Perhaps something could be done by replacing (at least allowing a configuration) cmd.exe with PowerShell.

How do you replace BAT files?

Trimbo — Sat, 19 May 2007 20:16:41 GMT

So, if people are using Powershell in place of CMD.exe, what are they doing about BAT or VBS files that are intended to be double-clicked to run?

Is there any roadmap or tool for this functionality? I haven't been able to find one. Or should we be making bat files that run powershell scripts? That seems ugly. :\

re: Replacing cmd.exe

PowerShell Team — Sat, 19 May 2007 18:04:19 GMT

I don't have a pointer but I belive that it was IT Forum in Nov 2005 that this was announced.

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

re: Replacing cmd.exe

Seth — Sat, 19 May 2007 14:48:07 GMT

I'd like to second that request please: where has Microsoft mentioned that VBScript support will eventually become an optional component? Is it the WSH as a whole that will become optional, hence, JScript support will be optional too? This will help to sell my company on transitioning to PowerShell. Thanks.

re: Replacing cmd.exe

Martin — Fri, 18 May 2007 11:24:52 GMT

I agree, Powershell as default shell is a good idea, removing cmd.exe is definitely not.

You mentioned that EOL of VBScript has been announced. Do you have a link to the announcement?