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.
I have some code that writes a file by saving a MemoryStream to a FileStream using MemoryStream.WriteTo(). After the file is closed it is opened up again to read some metdata…
This works about 80 – 90% of the time. The other 20% I get an exception saying the file is “in use by another process”.
Does FileStream.Dispose() not release resources synchronously? Is there something going on lower in Win32 land I’m not aware of? I’m not seeing anything obvious in the .Net documentation.
As “immediately” as possible. There can easily be some lag due to
outstanding writes, delay in updating the directory info etc. It could also be anti-virus software checking your changed file.This may be a rare case where a
Thread.Sleep(1)is called for. But to be totally safe you will have to catch the (any) exception and try again a set number of times.