Search found 150 matches

by clum09
Thu Dec 07, 2017 10:56 am
Forum: PrimalScript
Topic: Cmdlet Autocomplete & "In" autocomplete
Replies: 17
Views: 8393

Re: Cmdlet Autocomplete & "In" autocomplete

Attached is the file that you can test. Rename the extension from .txt to .ps1 and test it out. Test-In-For-loop.txt You can test to type the keyword "in" inside the Show-Usage function, and the PrimalSense will change the "i" to "I" once you hit the space bar to bring the cursor away from the lette...
by clum09
Tue Dec 05, 2017 12:19 pm
Forum: PrimalScript
Topic: Cmdlet Autocomplete & "In" autocomplete
Replies: 17
Views: 8393

Re: Cmdlet Autocomplete & "In" autocomplete

I don't know why your PrimalScript does upper case i in front of in like mine did. Attached is the screen shot after I tapped away from n character. This behavior does not happen in PowerShell Studio though.
by clum09
Tue Dec 05, 2017 12:04 pm
Forum: PrimalScript
Topic: Cmdlet Autocomplete & "In" autocomplete
Replies: 17
Views: 8393

Re: Cmdlet Autocomplete & "In" autocomplete

I don't know why your PrimalScript does not upper case the i in front of the in. My PrimalScript upper cases the i as soon as I tab the cursor away from the n character. It assumes that the in keyword is a parameter for some reason.
Image
by clum09
Tue Dec 05, 2017 10:33 am
Forum: PrimalScript
Topic: Cmdlet Autocomplete & "In" autocomplete
Replies: 17
Views: 8393

Re: Cmdlet Autocomplete & "In" autocomplete

The Azure for Active Directory version is 1.1.166.0. For the in casing, you can try copy the following for loop script onto a blank page of the PrimalScript's Editor. As soon as you change In to in on the first line, PrimalScript will upper case the i in front of in to In. foreach ($objUser In $unli...
by clum09
Tue Dec 05, 2017 7:56 am
Forum: PrimalScript
Topic: Cmdlet Autocomplete & "In" autocomplete
Replies: 17
Views: 8393

Re: Cmdlet Autocomplete & "In" autocomplete

When I unchecked the "Auto case correction" in "Text Editor" in "PrimalSense | PrimalSense Option" dialog, it stopped the auto casing for the "in" keyword, and it also stopped to autocomplete and auto case for the functions that I had within the script. For the Autosense of the Azure modules, I adde...
by clum09
Mon Dec 04, 2017 1:43 pm
Forum: PrimalScript
Topic: Cmdlet Autocomplete & "In" autocomplete
Replies: 17
Views: 8393

Cmdlet Autocomplete & "In" autocomplete

Product, version and build: 7.3.108 32 or 64 bit version of product: 64-Bit Operating system: Windows 10 32 or 64 bit OS: 64-Bit Hello, I have been unable to to have PrimalScript's PrimalSense to autocomplete the Azure Active Directory cmdlets in the Editor like it does on the PowerShell ISE. Is the...
by clum09
Tue Apr 19, 2016 5:52 am
Forum: PowerShell Studio
Topic: PV2 Packager failed to parse $args variable correctly
Replies: 8
Views: 2812

Re: PV2 Packager failed to parse $args variable correctly

Attached is the output from the $EngineArgs variable from SAPIEN. Yes, SAPIEN introduced the $EngineArgs variable into the packager to break the native PowerShell $args variable in PV2. That was what I said in my previous post. I checked the parameter block you pointed out to me. With parameter bloc...
by clum09
Mon Apr 18, 2016 12:34 pm
Forum: PowerShell Studio
Topic: PV2 Packager failed to parse $args variable correctly
Replies: 8
Views: 2812

Re: PV2 Packager failed to parse $args variable correctly

David, Attached is the screen shot of packager setting for the PV2 - the one that removed the dash (-) character from the packaged script. I remembered that this happened right after SAPIEN introduced $EngineArgs variable into both Power Studio and PrimalScript. Since SAPIEN introduced the $EngineAr...
by clum09
Mon Apr 18, 2016 10:59 am
Forum: PowerShell Studio
Topic: PV2 Packager failed to parse $args variable correctly
Replies: 8
Views: 2812

Re: PV2 Packager failed to parse $args variable correctly

David,

Attached is the versions of the two executables.
by clum09
Mon Apr 18, 2016 9:14 am
Forum: PowerShell Studio
Topic: PV2 Packager failed to parse $args variable correctly
Replies: 8
Views: 2812

PV2 Packager failed to parse $args variable correctly

Product, version and build: PowerShell Studio, 5.2.118 32 or 64 bit version of product: 64 bit Operating system: Windows 7 Professional 32 or 64 bit OS: 64 bit PowerShell Version: 2 Hello, I have a script that accepts the parameters from the command line. When I packaged this script using the SAPIEN...