Multiple times now I've wanted executables to enforce starting Unity projects with certain parameters and make it super seamless for the end user. This seams to be a very neat, practical and small solution for that, thanks.
Unless I am missing something, you recommended that we use a password when compiling our ps1 to exe. However, I did not see it explained how to do that. How do you do that? I want to protect my source code. Thanks.
Hi @TechnicalTerry, thanks for your question. We checked with Brien Posey, and here's what he said: "I don’t know why Windows didn’t freak out over an unsigned EXE. PS2EXE does not sign files, so I am not sure why Windows would not generate some sort of warning message."
Maybe im missing something, but why wouldnt I just coninute to use iexpress? Iexpress is built into Windows so no additional installs needed, and it can make exes of anything not just powershell scripts. Reinventing the wheel here?
@TheRambler7480, great question. Here's Brien Posey's response: "Iexpress is designed for building self-extracting executables. For instance, if you wanted to build an installer for an application, you would use Iexpress. To the best of my knowledge, you can’t use it to convert a PowerShell script into an executable. The best that it can do is to create a self extracting package that includes a PowerShell script and a command to execute it."
![ILLSLICK - KILLSHOT REMIX [FULL VERSION]](http://i.ytimg.com/vi/RIK8RrqIAzE/mqdefault.jpg)
Multiple times now I've wanted executables to enforce starting Unity projects with certain parameters and make it super seamless for the end user. This seams to be a very neat, practical and small solution for that, thanks.
Great video! I just started working with PowerShell and I think this will be a good solution for a few projects. Thanks!
why my non malicious code is being showed as virus when iam creating exe from it i tried to create exe of empty ps1 file still it said its a virus
Unless I am missing something, you recommended that we use a password when compiling our ps1 to exe. However, I did not see it explained how to do that. How do you do that? I want to protect my source code. Thanks.
Why didn’t Windows freak out because you were running an unsigned exe file?
Hi @TechnicalTerry, thanks for your question. We checked with Brien Posey, and here's what he said: "I don’t know why Windows didn’t freak out over an unsigned EXE. PS2EXE does not sign files, so I am not sure why Windows would not generate some sort of warning message."
Maybe im missing something, but why wouldnt I just coninute to use iexpress? Iexpress is built into Windows so no additional installs needed, and it can make exes of anything not just powershell scripts. Reinventing the wheel here?
@TheRambler7480, great question. Here's Brien Posey's response: "Iexpress is designed for building self-extracting executables. For instance, if you wanted to build an installer for an application, you would use Iexpress. To the best of my knowledge, you can’t use it to convert a PowerShell script into an executable. The best that it can do is to create a self extracting package that includes a PowerShell script and a command to execute it."
Nice. Thanks.