FileSystemWatcher - Limits on usage in a Windows Service

Are there any known practical/theoretical limits to the number of FileSystemWatcher objects I can have implemented in a single Windows service? Based on my research I know I can create the objects at run time and add them to an fsw collection for ease of handling. But when would I start to get into trouble with performance, etc. I need a general fsw service that can monitor multiple directories from each of many lines of business (each has there own directory structure). Thanks. Alan.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

i'm not sure, rare circumstances according to this a suggestion on a recovery procedure

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.