I am using a BinaryReader and BinaryWriter over a MemoryStream and am wondering what the issues are with Seeking the underlying stream while using a BinaryReader.
BinaryWriter provides a Seek function, and so there is apparently no problem. BinaryReader, however, does not provide a Seek and also implies in the documentation for it's BaseStream property that it does internal buffering which will mess things up if you Seek the underlying stream...or at least that is my reading of the docs. Can anyone clarify this a bit? Why is there no Flush or Seek or something on the BinaryReader and is my reading of the docs correct or am I misinterpreting them? Why is BinaryReader buffering anything in the first place? Isn't that just duplication of the buffering of the underlying streams and just a total waste of memory and cycles on a MemoryStream? Any info would be appreciated! DJ ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************
