Output Execute PowerShell Script Action Has Changed (FB 7.0.0 Build 3002)

FinalBuilder Bugs
1

Hi,The output of the Execute PowerShell Script Action produced in Build 3002 appends the string “Successfully Executed PowerShell Script” to the end of the result of the PowerShell script. It looks like it is missing a linefeed. Better still, since this is always appended I always need to parse the result of the Action, it would be better to be able to have an option to suppress that message. You could also wonder why the success/failure is in the result of the PowerShell script. An Action has a success/failure framework why not use that.Regards Alfred

2

Hi Alfred,

Thanks for checking with us about the powershell “Successfully Executed” end state. I have had a run through of a simple powershell script and some other scenario’s. Also installed some previous builds and found that the line “Successfully Executed Powershell Script” is always appended to the end of the powershell output in the FinalBuilder log.

When storing all the output into a variable the variable only contains the lines logged by the powershell script, as well as the extra success/failure line we add.

It appears the reason for the success message, is pairing with the failure message. The failure message will push out a result code which otherwise would not appear in the powershell script unless specifically written out.

I will have a chat with Vincent and see what we can do for you in the action. One of our main tenants is to avoid a “Mixing Desk” style of options.

3

Hi Jason,

Thanks. Just to clarify. The script does not give an error it gives me the result that I want. In builds before 3002 the “Succecss…” was appended on a new line, now it seems to be appended w/o. When using var.Split(vbCrLf,…) on the output I could separate them. now I don’t have the New Line anymore.

Regards Alfred

4

Hi Jason,

Another tidbit. I do see “Success…” on a new line in the Live Log. When I log to variable it becomes 1 line by the looks of it.

This is what I execute:

if (Test-Path -Path “%FileName%”) {
(Get-Acl “%FileName%”).Owner
}

5

Hi Alfred,

Great news, I have found the issue and fixed it. The build with the fix is located here;

http://downloads.finalbuilder.com/downloads/finalbuilder/700/FB700_3023.exe.

Just a note that this build is the latest collective build for FinalBuilder. Just as a quick note, it has fixes for the following things;

- FTP Upload creating empty directories.
- FTP Mirror performance and orphan file detection.
- SFTP Fixes.
- Fix for log to variable performance and line-endings.

6

Hi Jason,Thank you again for such a quick reply. Unfortunately build 3023 did not fix the problem.I could not attach a test project to this thread. If you would like to have it drop me an email.P.S. Note that I’m on Windows 8.1. Update 1Regards Alfred

7

Hi Alfred,

A test project would be great. If you could please send that to support@finalbuilder.com that will get to me.