AutoIt vs. PowerShell

[TXTechie]

Hello Everyone,

I know that this is an AutoIt forum and that everyone here loves AutoIt (as I do). But, I was hoping that some of you whom might have experience with PowerShell could provide me with a more objective comparison as to whether it makes more sense to use AutoIt or PowerShell as my primary "wrapper" for driving all of the software deployments within my company. Currently, I'm using VBScript for my "wrapper" template, but I'm seriously thinking about switching to either AutoIt or PowerShell.

Which one should I use and why?

[water]

You could use both. Call PowerShell from AutoIt.

Why:

AutoIt is easy to learn. Moving from VBScript to AutoIt shouldn't be a problem.

Powershell is powerfull. Some things that can't be done with AutoIt can be done using PS.

[keldepulo]

You could use both. Call PowerShell from AutoIt.

Why:

AutoIt is easy to learn. Moving from VBScript to AutoIt shouldn't be a problem.

Powershell is powerfull. Some things that can't be done with AutoIt can be done using PS.

 

with aut2exe you can create an encrypted executable script embedding everything you need, and than execute them everywhere (on every NT version ) without installing bloaded components ...

have you never tried to do this with vbscript or with powershell ?

[water]

Here is the >link how to combine AutoIt and Powershell.

[TXTechie]

Thanks, water! You make some great points - using AutoIt as my primary foundation or "wrapper" I have GUI functions AND I can use PowerShell from within AutoIt (even adding a GUI for PowerShell functionality)! The best of both worlds!

Does anyone else have any suggestions/input?

[water]

Just an observation.

I run PS from Autoit by directly calling powershell.exe to create an Exchange mailbox. It runs forever (about 30 seconds) and uses a huge amount of storage (about 160 MB).

So I use PS only if I can't avoid it.

[JLogan3o13]

I would agree with Water - I've used PowerShell in the past, but now only do so when I cannot accomplish something purely with AutoIt (which is rare).

[scubar]

I use AutoIt for the majority of my tasks.

I recently began using Powershell as its far easier/safer to accomplish Active Directory tasks in Powershell than in Autoit though.

[water]

I recently began using Powershell as its far easier/safer to accomplish Active Directory tasks in Powershell than in Autoit though.

Did you have a look at my AD UDF? I'm sure it is faster and easier than PS.

What do you think makes PS safer than AutoIt regarding AD?

[scubar]

No offence but I would just much rather use Powershell as it has been designed by Microsoft with an aim to make windows server based tasks easier.

The AD Cmdlets are so easy to work with it makes automating tasks a breeze

[JLogan3o13]

It is a personal choice, to be sure, scubar. I see AutoIt the same way - it has been designed to work with the Windows API, and to make tasks easier (not only server tasks). And from my personal use of the AD Cmdlets, I have only found one task out of literally hundreds of scripts that I could not do more easily in AutoIt. It's all about your experiences with a language, I guess

[water]

No offence taken

If you feel better using PS to interact with AD, fine. The AD UDF was started when there was no Powershell available.

As JLogan3o13 said: It is a personal choice.

[water]

icecola321,

is this post related to the subject? Don't understand what you try to tell us. Please use Google translate to create a meaningful english post.

[spudw2k]

with aut2exe you can create an encrypted executable script embedding everything you need, and than execute them everywhere (on every NT version ) without installing bloaded components ...

Mostly true, except for the "encrypted" part; the security (integrity) of a complied script has been discussed time and time again on this forum.

I didn't want to leave that (as slight as it may seem) hanging out there.  It could be ill or un-informed info, but I don't want other un-informed users to adopt it.

The ultimate lesson here is, don't script something you aren't willing to risk being seen by prying eyes (such as sensitive names, sites and credentials).

Sorry for the rant.

Anyways, both PowerShell and AutoIt are great.  I mostly have AutoIt experience and it has worked well for me.

[TXTechie]

I have also heard (and experienced some) of the slowness of PowerShell. Just another good reason to go with AutoIt.

I have decided to go ahead an migrate my template from VBScript to AutoIt.

I want to thank everyone for their input!

[spudw2k]

Despite what new members may think--specifically one's who want something for nothing or clearly disregard the rules--this forum is a great resource/community for learning; so please don't hesitate to ask for help when needed.

[TXTechie]

Thank you, spudw2k. And, I agree with you - this community has already helped me and if I'm going to be using AutoIt even more than I have in the past, I fully expect to be here in the forums more often. 

[Starstar]

I do not know about powershell. But i must say one thing "autoit is an easiest tool in programming". 

[water]

Adnan,

do you really think this helps the OP? Would be better posted in the Chat section.

[JLogan3o13]

I do not know about powershell. But i must say one thing "autoit is an easiest tool in programming". 

 

Adnan, every time you start spamming threads with these irrelevant posts you get warned by a Mod. How long before you actually learn?

Back on topic - the other big difference in my mind is GUI goodness in AutoIt. I much prefer building a GUI in AutoIt (despite the limitation in the look and feel of windows) rather than a wpf app in PowerShell.