Problem: during executable builds LabVIEW automatically generates temporary files in the build directory (in the uber cool l4bv13w directory this is created automaticall...). Unfortunately my automatic synchronisation tools that I use pick up these file system modifications and attempt to sync them to the cloud. This leads to two possible problems:
1) LabVIEW deletes the files before my sync tool has uploaded them (sometimes ok, sometimes the sync tool gets confused as it has already generated a file change list)
2) LabVIEW build fails as the sync tool is "holding" onto the file during upload.
Solution: These two problems could be mitigated if I could specify a temporary path during the build process that is not being automatically synced. The build could do whatever it wanted to this directory and only copy across the final files when it was done. This would also perhaps solve a problem when the build fails due to long path names, as something like c:\temp could be used for the build.
PS: I know this can mostly already be done by jumping through a few hoops using a post build actions and doing it "manually", but it would be nice if there was an easy way to do this within the build window
