FinalBuilder 8 (Build 941) - Copy Files actions failes to access files on network share -- propably because FileSet.FILE<INDEX> retruns paths with double quotes although not defined by FileSet

Hi!

As mentioned in my previous bug report (https://www.finalbuilder.com/support/forums/aft/16179), I’m trying to run a project which works with FinalBuilder 7 after converting it to FinalBuilder 8.

Now that the FileSet-file-by-index problem is fixed, I’m running into a new problem:

The FileSet operates on a windows network share ("\servername\share\dir") and lists all files as defined by the include/exclude patterns. The full path returned is correct and valid. Next, this path is used with a Copy Files action to copy the file from the network share locally. This actions fails with error message “File not found”.

Analysing the problem with Microsoft’s Process Monitor, it shows that the Copy Files actions concatenates the given source path (the full path to the file on the network share) with the base program directory of FinalBuilder: c:\Program Files\FinalBuilder 8"\servername\share\dir<br>
Note: the path which FinalBuilder tries to access includes one double quote followed by the base directory of the target file.

The Copy Files actions uses the file by index method to retrieve the first result of the Fileset. The Fileset has no quoting defined (Default quoting = None), therefore the FileSet.FILE-Method should use the same settings (according to http://wiki.finalbuilder.com/display/FB8/Accessing+FileSets: Specifying the quote type overrides the default quote type as specified in the FileSet Define action). But according to the Build Log, double quotes are added.

I could fix this by using “%FILESET.FILE0:quote=none%” - but “none” is not defined/mentioned in the documentation and it should use the default quoting of the fileset in the first place.

Greetings,
Chris

Hi Chris

Thanks for the report, I was able to reproduce and fix this here. There was a place in the parser that was not setting the correct default. I’ll upload a build with the fix shortly.

Hi Chris

A new build is up on the site with the fix for this.

Thanks - it works.

Greetings,
Chris