By my read, Position properties calls Seek() so the primary diff is the
former is a property and the latter is a method. On paper calling Seek
should be "slightly" faster as you don't call the Position property wrapper
first. Also, I think you end up calling FlushWrite twice if using Position
as it is called in Position and Seek, but have just glanced at the code.
--
William Stacey, MVP
http://mvp.support.microsoft.com
"PJ Olson" <pe*****@sux.com> wrote in message
news:e8**************@TK2MSFTNGP09.phx.gbl...
All, is there a speed or efficiency difference in using
FileStream.Position vs. FileStream.Seek to navigate through a file?