Quantcast
Channel: PS2EXE
Viewing all 87 articles
Browse latest View live
↧

Reviewed: PS2EXE v0.4 (Jan 08, 2014)

January 8, 2014, 10:41 am
$
0
0
Rated 5 Stars (out of 5) - Works exactly as designed, couldn't ask for anything more. Thanks for the hard work and sharing it!
↧
Search

New Post: Add support for extra files?

January 22, 2014, 5:35 am
$
0
0
First off - thank you for sharing this tool with the community. It works great!

Would you consider adding the ability to build in extra files? For example, if I have a batch file or dll that I want to call from my PS script. Maybe a folder instead of a single file?

I've been using the beta version (0.4.0.0) and it works great, no issues so far.

Thanks,
Tony
↧
↧

New Post: Add support for extra files?

January 22, 2014, 5:35 am
$
0
0
First off - thank you for sharing this tool with the community. It works great!

Would you consider adding the ability to build in extra files? For example, if I have a batch file or dll that I want to call from my PS script. Maybe a folder instead of a single file?

I've been using the beta version (0.4.0.0) and it works great, no issues so far.

Thanks,
Tony
↧

Reviewed: PS2EXE v0.4 (Jan 22, 2014)

January 22, 2014, 5:40 am
$
0
0
Rated 5 Stars (out of 5) - No issues, works great, simple and straightforward. Thanks!
↧

New Post: PowerShell 4.0 Support

February 7, 2014, 1:33 pm
$
0
0
Find this line
if($PSVersionTable.PSVersion.Major -eq 3) {
    $psversion = 3
    write-host "You are using PowerShell 3.0."
}
and add this line right above it
if($PSVersionTable.PSVersion.Major -eq 4) {
    $psversion = 3
    write-host "You are using PowerShell 4.0."
}
PowerShell v4.0 can use the same assembly version numbers as PowerShell v3.0 because .net 4.5 is backwards compatible.
↧
↧

Reviewed: PS2EXE v0.4 (helmi 17, 2014)

February 17, 2014, 11:17 pm
$
0
0
Rated 5 Stars (out of 5) - Really good tool does just what it says. Just what I needed! Thank you very much and keep up the good work. -Kalle
↧

New Post: Icon support

February 28, 2014, 3:15 pm
$
0
0
Nice Post...

Thanks for the icon script :)
↧

New Post: Convert back from executable to Powershell script

April 29, 2014, 9:50 am
$
0
0
ikarstein wrote:
Hi!

No problem! You could you the -extract parameter! - There are other ways too...

Ingo
Hey, great script - very useful!

I've got an exe created with this that needs modification, but when i use the -extract parameter, it is ignored.

What are the other ways I can get my script extracted then back up and running without rewriting it from scratch?
↧
Search

New Post: Convert back from executable to Powershell script

April 29, 2014, 11:20 am
$
0
0
Hi!

You can open the EXE file in ILSpy and look for the Base64-Encoded string. This string you can decode using an online tool or PowerShell.

Does it work?

Regards
Ingo
↧
↧

New Post: dot-included files

May 23, 2014, 11:45 am
$
0
0
How does this handle dot-included files?
↧

New Post: Suppress Import-Module Messages

June 9, 2014, 7:20 am
$
0
0
Hi, the conversion got very well and the script run correctly except for a similar problem of mugabemkomo.

Somebody has any idea how to solve? I have tens of:

parent = -1 id = 0 act = Completed. stat = Completed. cur = pct = -1 sec = -1 type = Completed
parent = -1 id = 0 act = Completed. stat = Completed. cur = pct = -1 sec = -1 type = Completed
parent = -1 id = 0 act = Completed. stat = Completed. cur = pct = -1 sec = -1 type = Completed
(...)

Thanks in advance!
Leo.
↧

New Post: Convert back from executable to Powershell script

June 19, 2014, 7:18 am
$
0
0
Hi,

is there a way to disable the -extract parameter?

is there a way to avoid any attempt to get the code?

Thanks!
Leo
↧

New Post: Convert back from executable to Powershell script

June 19, 2014, 2:33 pm
$
0
0
Hi!

It is easy to remove the the code for "-extract" so that the parameter will do nothing!!

Regards
Ingo
↧
↧

New Post: Convert back from executable to Powershell script

June 20, 2014, 2:05 am
$
0
0
Ok, it worked as I disabled "-extract" in the code. Thanks!

Then I tryed to understand how to use ILSPY 2.1 and get "Base64-Encoded string" as you suggested in a previous post but I couldn't manage to find this string. Please, could I have a little help?

Thank You!
Leo
↧

Reviewed: PS2EXE v0.4 (juil. 01, 2014)

July 1, 2014, 6:57 am
$
0
0
Rated 4 Stars (out of 5) - It may be my fault, but I have created scripts with named arguments (e.g. myscript.ps1 -Mode GUI) and it does not work after conversion. I had to create two (or more) exe files to make my tools work. Except this tiny issue, it's really great and simple
↧
Search

New Post: write-progress -activity "Progress Header" -status "Status line"

July 13, 2014, 7:07 am
$
0
0
Hi,
I just created the first exe-file.
My original powershell script uses write-progress to show something else then that what is displayed at console - but this fails:
Is it true, C# does not have an equivalent to powershell's write-progress?

Beside that I tried to mark and copy some lines in the opened console and failed.
Is there something that I can do to enable that?

Is there a way for the script to find out whether it is running as script (powershell -file "name.ps1) or as a C#-exe-program?
PowerShells: $ScriptName = $MyInvocation.MyCommand.Name seems not to work.

Thanks in advance
↧

New Post: The term '.\ps2exe.ps1 is not recognized

September 10, 2014, 12:35 pm
$
0
0
Hi, I'm quite new to PowerShell scripts so please forgive my naive questions. I've tried my best to convert my script to an exe with PS2EXE however I keep getting errors involving "The term '.\ps2exe.ps1 is not recognized as the name of a cmdlet, function, sc". I ran the callPS2EXE.bat and the createDemo.bat which worked perfectly but I can't seem to get it to run with my own script. So far I've tried to execute the conversion in PowerShell, PowerShell ISE, and CMD. I figure it is probably a syntax error I'm making somewhere somewhere since I don't have a great understanding of PowerShell yet. If anyone could assist me with this issue I would be extremely appreciative. Thanks!
↧
↧

New Post: The term '.\ps2exe.ps1 is not recognized

September 12, 2014, 4:23 am
$
0
0
Hi!

It is not easy to say what the problem is! - Normally .\ps2exe.ps1 only works from a PowerShell console (powershell.exe). You cannot start it this way from a Windows Command Line (cmd.exe). - Have you tried this?

Regards
Ingo
↧

New Post: The term '.\ps2exe.ps1 is not recognized

September 12, 2014, 11:52 am
↧

Created Unassigned: read-host -assecurestring [broken] [2434]

October 15, 2014, 3:30 pm
$
0
0
Read-host "Type your password here: " -assecurestring


After compiling it takes in the string as a regular string instead of a secure string. Text does not have * either as you are typing.

Is there an assembly I need to specifically add to get this to work?
↧
Viewing all 87 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>