Re: When using System.IO.FileStream, I write 8 bytes, then seek to the start of the file, does the 8 bytes get flushed on seek and the buffer become a readbuffer at that point instead of being a write buffer?

**=?ISO-8859-1?Q?Arne_Vajh=F8j?=** · Jul 31 '08, 10:35 PM

Re: When using System.IO.FileS tream, I write 8 bytes, then seek tothe start of the file, does the 8 bytes get flushed on seek and the bufferbecome a readbuffer at that point instead of being a write buffer?

Lloyd Dupont wrote:

VS is a good hexa editor, if you want to do some hexa read of your file...
"DR" <softwareengine er98037@yahoo.c omwrote in message
news:ufqDNzR8IH A.1200@TK2MSFTN GP04.phx.gbl...

>When using System.IO.FileS tream, I write 8 bytes, then seek to the
>start of the file, does the 8 bytes get flushed on seek and the buffer
>become a readbuffer at that point instead of being a write buffer?

I think you could test that for your self, couldn't you! ;-)

He could.

But there would not be much point. At least not if the test
were successful.

I assume that the poster is interested in knowing what .NET
guarantees not what his .NET version on his Windows version
with <insert 1000 other factorsgive.

Arne

Re: When using System.IO.FileStream, I write 8 bytes, then seek to the start of the file, does the 8 bytes get flushed on seek and the buffer become a readbuffer at that point instead of being a write buffer?

Re: When using System.IO.FileStream, I write 8 bytes, then seek to the start of the file, does the 8 bytes get flushed on seek and the buffer become a readbuffer at that point instead of being a write buffer?

Comment