If I create an instance using the override with the path and file I can have this fire once correctly within the automation then it never fires again. When using it from the global container it never fires and seems to generate a path error whenever enable raising events is true. I setup a smaller test application to try and resolve the issue I'm seeing. I'm setting the filesystemwatcher properties and trying to display a message when a change, etc is fired. All the properties come through, but when I attempt to set Enable Raising Events to True and it doesn't pick up the value. Is there an order you have to pass these values in? Path, Filter, and NotifyFilter seems to be fine.
Posted: 4 years ago
Posted: 28 Mar 2018 9:34 EDT
Thomas Sasnett (ThomasSasnett)
Lead Robotics Architect
The requirements changed for the project which no longer requires watching the directory. I will look at the sample solutions and see if I can have it work with the previous version of my solution just to see it work.