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?

I think you could test that for your self, couldn't you! ;-)
VS is a good hexa editor, if you want to do some hexa read of your file...

"DR" <softwareengineer98037@yahoo.comwrote in message
news:ufqDNzR8IHA.1200@TK2MSFTNGP04.phx.gbl...

Quote:

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?
>

Lloyd Dupont wrote:

Quote:

VS is a good hexa editor, if you want to do some hexa read of your file...
"DR" <softwareengineer98037@yahoo.comwrote in message
news:ufqDNzR8IHA.1200@TK2MSFTNGP04.phx.gbl...

Quote:

>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?

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: 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?

Similar C# / C Sharp bytes

/bytes/development

/bytes/it

/bytes/about