How do you run without a CMD window?

[mqh77777]

I created a new Project. I created this on a Windows 7 x64 workstation but when I did a "build" I built it for PS 2.0 and x86. all of our Windows 7 workstations are running PS 2.0 on a 32-bit OS.

when I run the compiled .EXE it pops up my GUI but it also pops up a CMD window. We don't want that. I want it to be 100% GUI.


How do I make this run without a CMD window?

[davidc]

I moved this to the product forum since it isn't a scripting question.

When making your packaged executable, select the following engine:

SAPIEN PowerShell V2 Host (Windows Forms) Win32

David

[davidc]

Both Windows and Windows Form engines will hide the console window. The difference between the two is that the Forms engine suppresses all output and the Windows engine pops up message boxes for output.

David

[mqh77777]

ok, I click on the Deploy Tab\Build. From there I have a Script Packager options window. Under PLATFORM I do NOT have any executable options. I only have (command line) & (Windows forms)

so I picked (Sapien PowerShell v2 Host (Windows Forms) Win32. Now when I run my tool it does not complete. It should prompt me for "computer name" and "message to send" I only see the first prompt, not the second so my NetSend message never runs.

Do I have the right version of this tool? or am I missing functionality?

[davidc]

What are you using to prompt the users? This really depends on what you are doing in your script.

When using a GUI I recommend incorporating the input into the form or create a separate form to handle the input.

David

[mqh77777]

I have created 1 form. On this form I have 2 buttons. Here is the exact code for each button.

$buttonSendMSGTo1Computer_Click={
#TODO: Place custom script here
$computer = Read-Host -Prompt "Enter a single computer name"
$Message = Read-Host -Prompt "Enter your message here"
msg /SERVER:$computer * /TIME:200 $Message
}




$buttonSendMSGToAllComputer_Click={
#TODO: Place custom script here
import-module activedirectory
$Message = Read-Host -Prompt "Enter your message here"
New-Item -ItemType directory -Path "C:\Temp"
(Get-ADComputer -Filter * -SearchBase "ou=mgh_workstations,dc=acmel,dc=org").Name | Out-File c:\temp\allWin7.txt
$pc = Get-Content "c:\Temp\allWin7.txt"
foreach ($desktop in $pc)
{
msg /SERVER:$desktop * /TIME:2000 $Message

}
remove-item "c:\Temp\allWin7.txt"
}


So each button when pressed launches a new pop-up window that you enter text into. When I compile this into an .EXE and run it the pop-up is Not in the form of a GUI but it launches a .CMD window to ask me the computer name/message.

[davidc]

As I mentioned you are better off using your own custom GUI instead of relying on Read-Host.

The Window Forms engine isn't meant to be used for Host output or input. Try using the Windows engine instead of the Forms engine and see if that makes a difference.

I recommend reading this article:

http://www.sapien.com/blog/2012/06/04/u ... istrators/


David