transcript from winform script

[LtMandella]

Product, version and build:studio 2015
32 or 64 bit version of product:64 bit
Operating system: win server 2008 r2
32 or 64 bit OS: 64

I am not having any luck getting a transcript in a wonforms script to work as expected.

Is there a recommended way to get a transcript type log from a winform script? I don't expect to see a transcript of all the users interactive winform activity, but I'd like to get a complete transcript of all the powershell script execution up to the moment the winform opens.

I have written scripts completely by hand that run winforms and in those start-transcript outputs a very useful and verbose transcript.

thanks,
ken

[davidc]

[POST MOVED TO POWERSHELL GUI FORUM BY MODERATOR]

[jvierra]

What is it that is not working? Did you specify the complete path to the transcript file?

[LtMandella]

Hi jvierra,

Here is what I am doing to get this to work. Probably I am doing it all wrong and there is a better way

I want to audit ALL possible errors and a numerous object properties, arbitrary text from output inside the functional script, etc. So my usual practice is to always call my "functional" script from a parent "logging" script.

Basically the "parent" script will always look like this:
---------------------------------------------------------
Start transcript -path c:\blah\auditfilename.txt

Invoke-Expression "\\somepath\somefunctionalscript.ps1 `'$inputList`' `'$CommaListParams`'"

Stop-Transcript
--------------------------------------------------------------

This way even if the functional script won't compile/execute, I still capture and persist useful info about the problem.

To make this work with a winform script, I have to hack the .psf file after export of the .ps1 and remove the "Out-Null" from the call to the .psf at the end of the generated .ps1 export file.

Is there a better way?

thank you!
Ken

p.s. pshell studio 2015 is one of the best tools I have ever used (in a long career)...

[jvierra]

Why? Why don't you just add the Start-Transcript to the body of the form file and run it?
-

[jvierra]

Ok - I see it. IK have always been unfavorable about this technique for launching a script. Maybe now we can get it fixed.

Not sure about this. Maybe the guys at Sapien can come up with a fix. I will flag them. Meanwhile can you post your issue to the Customer Service forum?

[LtMandella]

Thanks for the reply, I will post in customer service (although was it moved from there one time already?)

[[ I have always been unfavorable about this technique for launching a script]]

If you get a moment, could you recommend alternative?

thanks again,
ken

[Alexander Riedel]

FYI, the customer service forum is not the correct place for product support.
The "Customer Service" forum is for non-product specific questions, e.g. your SAPIEN account.
The appropriate place is the forum for the specific product, in this case the "PowerShell Studio" forum.
viewforum.php?f=12

[jvierra]

Thanks for the reply, I will post in customer service (although was it moved from there one time already?)

[[ I have always been unfavorable about this technique for launching a script]]

If you get a moment, could you recommend alternative?

thanks again,
ken

Right now your workaround is the only one. Perhaps the programmers at Sapien can add an option to not use Out-Null. With Out-Null all output is tossed and does not get sent to the transcript engine. This is due to running a medal form which delays all output.

In many forms we like to grab the form object. It has long been my feeling that returning th form object on DialogResult::OK is more useful. This would alos preclude the need for Out-Null.
if($form.ShowDialog() -eq 'Ok'){ %form}

To detect result we can just:

Code: [Select all] [Expand/Collapse] [Download] (Untitled.ps1)

1. if($frm=Call-MyForm_psf){
2.     #process $frm - $frm contains all data
3. }

I suspect this would have to be an option as so many scripts are designed on the current method.

Another workaround would be to generate a script file and run it in the CLI of PowerShell. It is still multi-step but does not require the manual edit.

[jvierra]

FYI, the customer service forum is not the correct place for product support.
The "Customer Service" forum is for non-product specific questions, e.g. your SAPIEN account.
The appropriate place is the forum for the specific product, in this case the "PowerShell Studio" forum.
viewforum.php?f=12

Sorry - I typed without thinking.