Could anyone please explain to me the differences, if any?
I tried to Google it but couldn’t find much information. Maybe I didn’t use correct keywords.
Any insight would be greatly appreciated.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Could anyone please explain to me the differences, if any?
I tried to Google it but couldn’t find much information. Maybe I didn’t use correct keywords.
Any insight would be greatly appreciated.
As far as I can tell, at least for this specific case, nothing.
Both method Seek() and property Position require CanSeek to be true so from what I see it’s up to the implementer.
Seek is really there to allow searching from specified locations (SeekOrigins) to an offset (the examples given on MSDN are somewhat convoluted but representative of the purpose: http://msdn.microsoft.com/en-us/library/system.io.filestream.seek.aspx).
Position is absolute and is obviously not meant for searching.
The case you mentioned just happens to be equivalent.
Personally, I’d use .Position = 0 to move to the beginning of the stream as that reads cleaner to me than “Seek using the beginning of the file as an origin and move this 0 offset of bytes.”