I have the following code block which is giving me a headache.
Logically it should work as I am using the filestream providing the lock within the using statement.
Try Thread Synchronization. You can find more details from this link.
The FileShare.None flag does not cause threads to queue, it just locks the file, hence the exception that you get. To provide mutually exclusive access you can lock a shared object prior to writing.
But you say this "Now my program is a multithreaded application. Any thread could be trying to write to this file." Now, do these threads all use exactly the same method to write to the file? Let's assume they do, then this should work ...
Create a static class variable ...
private static object lockObject = new object();
Use it here ...
lock (lockObject)
{
using(var sw = new StreamWriter(fs))
{
sw.Write(str + text);
}
}
I have made some assumptions about the threads, so you may have to look up info on synchronization if this doesn't work or provide some more info to us.
Also, please close your StreamReader
earlier (in case the method returns earlier). Close it immediately after you use it or better yet use using
.
As in the MSDN reference the Close method
Closes the StreamReader object and the underlying stream, and releases any system resources associated with the reader.
Thus it seems that the subsequent call to StreamWriter fails to use a closed resource, giving you the message "the file is not writable".
Try this
using (var fs = File.Open(path, FileMode.Open, FileAccess.ReadWrite, FileShare.None))
{
using (var sr = new StreamReader(fs))
{
var str = sr.ReadToEnd();
// ...
using (var sw = new StreamWriter(fs))
{
// ...
}
}
}