32 or 64 bit version of product: 64bit
Operating system: Windows 7 Enterprise & Windows 10 Enterprise (1809)
32 or 64 bit OS: 64bit
I have been programming with PrimalScript since 2002. (Just so that you know where I am coming from)
I have taken a deep dive into Windows Forms, in the last two months, using PowerShell Studio, now that I have a REAL BIG NEED for a GUI on top of a PowerShell Script.
I must complement all at SAPIEN for the GREAT tool for creating GUIs in PSS.
Also many thanks to June Blender for her very basic/generic straight forward videos in YouTube. They gave me the start that I needed to jump right in.
Some of the videos from LazyWinAdmin are also very helpful, thanks to those people also.
Now to my problem I have the need to pass some command line parameters to the script/form at start time, and then also through the EXE built from the deploy tool.
Where is the logic to be placed, exactly?
I put a normal PS1 style Param() section at the top of the PSF file, outside of ANY function definitions and that works when either hitting Run button or in Debug button in PSS.
BUT sometimes when I am trying to debug PSS DOES NOT STOP AT ANY of the Breakpoints that are set! (When in Debug mode of course)
It has done so before and then at other times it does NOT.
I read something in the Internet that you have some functions for passing and evaluating the command line Parameters, Convert-CommandLineToDictionary() and Parse-Commandline(), but it was NOT clear to me where exactly the code was to be placed.
I have looked at June Blenders URL:
Code: Select all
Would you guys please give me some more detailed examples of exactly where these functions are supposed to be placed?
If the code outside of the function blocks should NOT be used or is unreliable why does PSS not warn me about that code?