This is a synchronous method, which will block its thread both while waiting and while working on the thread. using some sort of timer or DateTime.Now as a better alternative For most things it's probably fine, but if you need precision over a long time span, consider if its a very long wait this will acumulate very small errors. you could do the sleep in here, but its probably a good idea to exit the error handler as soon as possible
don't forget to either return from the function or break out fo the while loop Static void safeCopy(string src, string dst, int timeout) / how long to keep trying in milliseconds The code here uses File.Copy, but it works just as well with any of the static methods of the File class: File.Open, File.ReadAllText, File.WriteAllText, etc. That way there is no elapsed time between the check and the opening, the OS does them at the same time. The basic resolution is to just try to open the file inside a catch block so that if its locked, you can try again. Its really hard to track down the sporadic Cannot copy the file, because it's used by another process error if you aren't looking for it too. The problem is this: the file can become locked between the time that you check it and the time you actually open the file. A bit of an unusual situation, but it definitely highlighted for me the problems with the 'check if the file is locked, then open it if it's not' approach. So, having glanced quickly through some of these and other similar questions I went on a merry goose chase this afternoon trying to solve a problem with two separate programs using a file as a synchronization (and also file save) method. If (_waitingForClose.Contains(e.FullPath)) Public static void listener_Changed(object sender, FileSystemEventArgs e) Something like (incomplete catch specific exceptions, initialize variables, etc): public static void listener_Created(object sender, FileSystemEventArgs e)
So, if the copy fails, (catch the exception), add it to a list of files that still need to be moved, and attempt the copy during the OnChanged event. OnCreated event will be raised immediately, followed by one or more Is being copied or transferred into a watched directory, the The OnCreated event is raised as soon as a file is created. If ((ex2 is IOException) & (errorCode = ERROR_SHARING_VIOLATION || errorCode = ERROR_LOCK_VIOLATION))įrom the documentation for FileSystemWatcher:
Int errorCode = Marshal.GetHRForException(ex2) & ((1 << 16) - 1) _log.WriteLog(ex2, "Error in checking whether file is locked " + file) Stream = File.Open(file, FileMode.Open, FileAccess.ReadWrite, FileShare.None) check that problem is not in destination file or does not exist (has already been processed)Ģnd Method: const int ERROR_SHARING_VIOLATION = 32 Stream = file.Open(FileMode.Open, FileAccess.ReadWrite, FileShare.None) You can call the following function until you get the False value.ġst Method, copied directly from this answer: private bool IsFileLocked(FileInfo file) There is only workaround for the issue you are facing.Ĭheck whether file id in process before starting the process of copy.
0 kommentar(er)
