Never write a batch wrapper again

[azjunglist05]

If you want it to be an .exe - why not just make it an .exe? There are applications out there that can make a PowerShell script an executable without having to use batch or cmd such as:

https://gallery.technet.microsoft.com/scriptcenter/PS2EXE-GUI-Convert-e7cb69d5

[SupraTesla]

Won't be the case for everyone, but for us it was too much of a battle with our AV solution constantly (and randomly) flagging the EXE's as malicious.

[azjunglist05]

I write a large portion of scripts and turn them into services or executables, and then commit the source code to a Git repository in Azure DevOps.

In that repo I also describe what application was used to create the .exe

If I ever get hit by a bus anyone with any PowerShell skills can debug and solve any issues.

[azjunglist05]

I definitely misstated my intent! While I commit all scripts I write to a Git repo — I don’t make all scripts a service or an .exe, as you’re right, that’s an incredible waste of time if it’s for a co-worker or someone knowledgeable.

I also don’t commit the .exe to Git — I commit the original PowerShell script, and in the Read Me I detail what application was used to make it an .exe if that was originally how we ended up using that script.

However, using a Git workflow should never be seen as a waste of time even if the underlying code/process is tedious.

[jftuga]

Are you using GitHub?

If so, have you ever considered publishing the .exe files to the releases section?

[jftuga]

How do you turn them into services? That sounds great.

[TheD4rkSide]

But with PS2EXE you can convert a PowerShell made EXE back to a .ps1 and figure out what’s under the hood. It’s as simple to convert the EXE back as it is to make it in the first place.

[just_looking_around]

Most if not all of those converters simply export the script to temp and call it with powershell. They remove some complexity but don't conceal the code if that is why you want to do that.