I have to doublecheck if this is the case.
When using the fileSystemWatcher in the application
where an event is checking for Changes in a file.
With just starting the application where no changes events is fired at all
the processor (AMD double core) Peeks at 50 % constantly.
Is this what happens when using the fileSystemWatcher ?
I use the _Changed event and NotifyFilter "LastWrite".
When opening the Form that contains the fileSystemWatcher the processor will in about 15 seconds go up to 50% constantly.
No events is fired here yet.
Anyone that has a clue about this, Should this be the case since it is an event ?
I use the _Changed event and NotifyFilter "LastWrite".
When opening the Form that contains the fileSystemWatcher the processor will in about 15 seconds go upp to 50% constantly, looking in TaskManager.
No events is fired here yet, so I wonder why this is happening.
Anyone that has a clue about this, Should this be the case since it is an event ?
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.