-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for 'Command' WorkingDirectory #42
Comments
I have added the working directory tag to the 1.5.2 beta release: https://github.com/TechieGuy12/FileWatcher/releases/tag/1.5.2-beta.1. Check to see if it works for you? |
Hi, Thanks for responding.
I tried with and without trailing backslash, ( i.e. Repo2\ ) but no luck I can't see what you changed since there is nothing to compare in commit 3ab7185; Could you add logging to confirm WorkingDirectory is being read correctly and/or actually used? Again, thanks for your time :) |
I forgot to mention the tag in the XML file is workingDirectory with a capital 'D'. The commit for the beta is in the develop branch. |
Working as expected with the right syntax :) I presumed all lower case based on 1) my original example config and 2) all lower case used for other config multiword tags, i.e. waitbefore Again, thanks for fix :) |
Hello and thanks for FileWatcher!
I am currently using FW to monitor file changes and run an EXE on a change.
My issue is that the command line executable I'm running uses the "WorkingDirectory".
I can work around this limitation if I launch FW.exe from the desired "WorkingDirectory", i.e.
C:\Users\User\Desktop\Repo1>c:\Portable\FileWatcher\fw.exe
However, if I need to monitor files from two different folders (i.e. define two configuration xml nodes), I can't run FW from both folder locations :)
[Unless I run two instances of FW?]
Therefore, does it make sense/possible to add a 'WorkingDirectory' XML 'Command' sub-node in the configuration file which would be applied when the EXE is run?
i.e.
`
Thanks in advance for your time :)
The text was updated successfully, but these errors were encountered: