Is it "wise" to use the "using()" statement while reading, and writing to the file system in NT? I actually read the file in without using() because it's a one time shot in the OnStartUp() method and I "sr.Close()" the file when it's done, but when writing I have a:
using(StreamWriter sw = new StreamWriter([file]))
{
sw.WriteLine("blah");
}
Each time a tick comes in. Is that too much overhead? Is there a more effiicient way? I'm experimenting because I've been getting "cannot access [file], it is being used by another process" (something similar) when trying to switch back and forth between diff. instruments/time frames in same chart window. This happens on and off, and I haven't figured out *exactly* which moves create that error. I'm assuming the write is staying open while the read is trying to access, hence the using() approach.
using(StreamWriter sw = new StreamWriter([file]))
{
sw.WriteLine("blah");
}
Each time a tick comes in. Is that too much overhead? Is there a more effiicient way? I'm experimenting because I've been getting "cannot access [file], it is being used by another process" (something similar) when trying to switch back and forth between diff. instruments/time frames in same chart window. This happens on and off, and I haven't figured out *exactly* which moves create that error. I'm assuming the write is staying open while the read is trying to access, hence the using() approach.
Comment