command line vs powershell code example

Example 1: powershell vs cmd

"PowerShell"		Command Prompt 
"PowerShell was introduced in the year 2006" CMD was introduced in the year 1981.
"It can be opened from run by typing PowerShell." It can be opened from run by typing cmd.
"It can operate with both batch commands and PowerShell cmdlets." It can work only with Batch commands.
"It provides the ability to create aliases for cmdlets or scripts. This can help the user to navigate between the functions easily." It doesn’t support the creation of aliases of commands.
"Output from a cmdlet can be passed to other cmdlets." Output from a command can’t be passed on to other commands.
"Output is in the form of an object." Output from a command is just text.
"Can execute a sequence of cmdlets put together in a script." In cmd, a command must be finished before the next command is run.
"Help command is available to get information regarding any cmdlets." No such help option is available for information regarding commands.
"It has an ISE." There is only a command-line interface, no separate ISE.
"It has access to programming libraries as it is built on .NET framework." No such access to libraries.
"It can integrate directly with WMI." Need some external plugin for WMI interaction.
"I can connect with Microsoft cloud products." It doesn’t have the ability to connect with MS online products.
"Supports Linux Systems." It doesn’t support Linux systems.
"It can be used to run all types of programs." It can run only console type programs.

Example 2: powershell vs cmd

** ** PowerShell    	vs  	Command Prompt  ** ** 
** PowerShell was introduced in the year 2006.	cmd was introduced in the year 1981.
** It can be opened from run by typing PowerShell.	It can be opened from run by typing cmd.
** It can operate with both batch commands and PowerShell cmdlets.	It can work only with Batch commands.
** It provides the ability to create aliases for cmdlets or scripts. This can help the user to navigate between the functions easily.	It doesn’t support the creation of aliases of commands.
** Output from a cmdlet can be passed to other cmdlets.	Output from a command can’t be passed on to other commands.
** Output is in the form of an object	Output from a command is just text.
** Can execute a sequence of cmdlets put together in a script.	In cmd, a command must be finished before the next command is run.
** Help command is available to get information regarding any cmdlets.	No such help option is available for information regarding commands.
** It has an ISE.	There is only a command-line interface, no separate ISE.
** It has access to programming libraries as it is built on .net framework.	No such access to libraries.
** It can integrate directly with WMI.	Need some external plugin for WMI interaction.
** I can connect with Microsoft cloud products.	It doesn’t have the ability to connect with MS online products.
** Supports Linux Systems.	It doesn’t support Linux systems.
** It can be used to run all types of programs.	It can run only console type programs.

Example 3: powershell vs cmd

** ** PowerShell    	vs  	Command Prompt  ** ** 
** PowerShell was introduced in the year 2006.	cmd was introduced in the year 1981.
** It can be opened from run by typing PowerShell.	It can be opened from run by typing cmd.
** It can operate with both batch commands and PowerShell cmdlets.	It can work only with Batch commands.
** It provides the ability to create aliases for cmdlets or scripts. This can help the user to navigate between the functions easily.	It doesn’t support the creation of aliases of commands.
** Output from a cmdlet can be passed to other cmdlets.	Output from a command can’t be passed on to other commands.
** Output is in the form of an object	Output from a command is just text.
** Can execute a sequence of cmdlets put together in a script.	In cmd, a command must be finished before the next command is run.
** Help command is available to get information regarding any cmdlets.	No such help option is available for information regarding commands.
** It has an ISE.	There is only a command-line interface, no separate ISE.
** It has access to programming libraries as it is built on .net framework.	No such access to libraries.
** It can integrate directly with WMI.	Need some external plugin for WMI interaction.
** I can connect with Microsoft cloud products.	It doesn’t have the ability to connect with MS online products.
** Supports Linux Systems.	It doesn’t support Linux systems.