Problems creating Windows Service-based multiple file watchers


just wondering if sound design.

i'm creating c# windows service in vs2012.  the basic concept don't know how many folders might watching filesystemwatchers instantiated dynamically (according database table) , added list.  the fsws have been extended through inheritance give them individual ids.   fsws use same event handlers since need behave identically.  just generate email , database log table entry of event.

i aware of behavior problems involving change event.  

what has me wondering behavior in scenario.  i have 2 separate folders being watched 2 separate instances of fsws.  if dump file either folder created event expect.  

if cut file 1 watched folder , paste other, deleted event of first folder. 

does sound familiar?  so far can see these 2 separate instances should acting independently of each other.

please handle onrenamed event.

as per msdn :

'the operating system and filesystemwatcher object interpret cut-and-paste action or move action rename action folder , contents. if cut , paste folder files folder being watched, the filesystemwatcher object reports folder new, not contents because renamed.

notified contents of folders have been moved or copied watched folder, provide onchanged and onrenamed event handler methods'


regards, http://www.shwetalodha.blogspot.in/



Visual Studio Languages  ,  .NET Framework  >  Visual C#



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

job syspolicy_purge_history job fail in sqlserver 2008

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'