Automation: WMIC And PowerShell Command's

With WMIC becoming "un-used" (I'm uncertain if it actually won't be used in the future)...

Is there any projection of Microsoft deprecating the dos batch language?

They haven't said anything like that yet, and it would be a huge undertaking. They generally deprecate things for many years before they are removed, so it would be well-known. It would be a huge thing to remove cmd or batch.

Currently, I use Windows "*.bat" and Linux-based "*.sh".
Is there a scripting language that can be used by both Windows and Linux-based?
(i.e., Python, Perl, etc)

Try3 said:

Do note that the member who posted this is on build 28020.1362

Click to expand...

It also applies for clean install of 25H2. I had problems installing AMD chipset drivers because of it.

WyattCollins said:

Currently, I use Windows "*.bat" and Linux-based "*.sh".
Is there a scripting language that can be used by both Windows and Linux-based?
(i.e., Python, Perl, etc)

Click to expand...

I'll start a new thread for the quoted post.
It's potentially redirecting from the original idea of this thread.

WyattCollins said:

Currently, I use Windows "*.bat" and Linux-based "*.sh".
Is there a scripting language that can be used by both Windows and Linux-based?
(i.e., Python, Perl, etc)

Click to expand...

PowerShell 7 on Linux. But seriously, most of the industry is standardizing on Python.

PERL still exists, but now ignored since it's annoying idiosyncrantic (look how often people brag about obtuse PERL code). PERL used to have an advantage in available libraries, but Python has caught up.

But PowerShell is what you learn to administer Windows. A lot of high-level or portable code is written in Python, but those devs don't have the Windows API hooks that the PS devs enjoy (because they have source code access).

WyattCollins said:

Is there a scripting language that can be used by both Windows and Linux-based?
(i.e., Python, Perl, etc)

Click to expand...

WyattCollins said:

I'll start a new thread for the quoted post.

Click to expand...

But you've already answered your question.
Python Releases for Windows
Python on Linux: A Comprehensive Guide - linuxvox.com


Denis

The replacement of WMIC has been answered.
All of my subsequent questions have been answered.
Cmd and PS isn't going away soon.
Python seem's to becoming a shared language between Windows and Linux.
Maybe use Python to create executable file for the respective kernel and/or shell.

Is it wise to use Python to automated end-user task's?

WyattCollins said:

Which scripting language's are installed by default in Windows

Click to expand...

WyattCollins said:

I know .bat .ps1 ,cmd

Click to expand...

Once again you've answered the new question.
You're really on a roll today.

There's no reason to expect any of those three to die any time soon.
[Unlike VBScript which is deprecated & which might die with 26H2.]
The next time I sit down to review my own scripts, I "intend" to study PS properly for the first time.
my ditty - Batch file and PowerShell guides [post #7] - ElevenForum


Denis

I believe my thoughts are beginning to have me going in circles.
I'm gonna stop and take a breather and try to slow my roll and calm my thoughts.

Try3 said:

The next time I sit down to review my own scripts, I "intend" to study PS properly for the first time.
my ditty - Batch file and PowerShell guides [post #7] - ElevenForum


Denis

Click to expand...

Do you have an "itinerary" that you follow for "proper study" for your purpose?

Thanks to everyone for the help's.

WyattCollins said:

"itinerary"

Click to expand...

No.
I have an aspiration but I also have abundant laziness & an awful lot of distractions.
I'll probably look over the TenForums guides in my linked list again first then study Learn PowerShell Scripting in a Month of Lunches as it seemed quite good to me [on a swift perusal] so I bought it.
One of my primary goals will be writing PS equivalents to replace my existing VBScripts but I want to study the subject properly so I write them in a well-structured way instead of continuing my current ad-hoc approach and then maintain them well [and not by just chucking in things then hoping for the best & fiddling with them until they more-or-less work].


Best of luck to you,
Denis

Thank you.
Sound's like something I need to improve on.

Is it possible to use Python to convert back n forth between "*.sh" and "*.ps1"?
Or did I already answer that one too? :/

Please pick a lane!!

PS kinda resembles Bourne shell scripting, because it was partially inspired by it. When Jeff Snover first tried to sell the idea of PS's predecessor, it was essentially an UNIX-like shell but with Windows bindings for system calls.

The major difference is everything in an UNIX shell is parsing output, piped as a text stream. You redirect output from one app, to another tool like grep or awk, and then redirect it again before you accept the results as your data.

With PS, you don't need a grep or awk to do the parsing. The language does that natively.

The major step forward in PS, is when you pipe the results of a built-in command, it can send a complex data object and not simple a string of text. A single command call can return multiple details in one pass. Then you "pick" at the returned object to grab which details you're interested in. It's very powerful.

And when you can't do something in PS, you just call an external executable. And you can redirect the output.

CMD, Python and PowerShell are all distinct programming languages. If you know UNIX shell scripting, PS will look familiar. If you know C, Python is somewhat close. CMD is a totally obtuse beast for parsing strings, if you're coming from an UNIX/Linux background. I was an UNIX admin for two decades, before moving to Windows.

Batch scripting is a terrible (and limited) programming language. And before the arrival of PS, everyone just had to learn how to program in an inferior manner. PS was designed for Windows admins, which is probably why it confuses casual users who don't program or do admin work.