Maximum-length reached: file change the quickest possible

[Ricardo Vazquez]

I'm writing log information into a file (via StreamWriter).
When it reached a 4GB size, my MFC/C++ code copied that file to another
name, truncated its length to 0 (CFile::SetLength(0)), and continued writing
(no need to close and open, so that it was very quick).

How is it the best .net way to get this "file change" the quickest possible?

Thanks!

Ricardo Vázquez.
Madrid, Spain.

 

[Jon Skeet [C# MVP]]

I'm writing log information into a file (via StreamWriter).
When it reached a 4GB size, my MFC/C++ code copied that file to another
name, truncated its length to 0 (CFile::SetLength(0)), and continued writing
(no need to close and open, so that it was very quick).

How is it the best .net way to get this "file change" the quickest possible?

I wouldn't copy the file at all - I *would* close it, rename it, and
then start a new one. That's likely to be much quicker than copying 4GB
of data over.