Re: FileSystemWatcher invalid directory name
- From: Samuel R. Neff <samuelneff@xxxxxxxxxx>
- Date: Thu, 14 Jun 2007 22:30:12 -0400
Yes, we use FileSystemWatcher in an asp.net app using impersonation.
We impersonate the authorized user when setting up the watcher and
then again when the event is raised ('cause event is raised on a
different thread).
It works fine when the unc is correct and setup. When we install our
app in an environment where the unc share is not setup properly, we
get no error, just no events.
Sam
------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.
On Thu, 14 Jun 2007 19:11:01 -0700, stahlerw
<stahlerw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am running it on my machine under a domain account that has access..
I have also noticed that I get the error the first time I create a new
document in the directory, subsequent attempts don't trigger or raise an
error.
So just to verify, you have seen it work with UNC path?
- References:
- Re: FileSystemWatcher invalid directory name
- From: Samuel R . Neff
- Re: FileSystemWatcher invalid directory name
- Prev by Date: Re: Tread Problem
- Next by Date: About Asynchronous method invocation
- Previous by thread: Re: FileSystemWatcher invalid directory name
- Next by thread: Re: FileSystemWatcher invalid directory name
- Index(es):
Relevant Pages
|
