Home/ Questions/Q 650553
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T22:03:56+00:00

In the past I’ve always used a FileStream object to write or rewrite an

  • 0

In the past I’ve always used a FileStream object to write or rewrite an entire file after which I would immediately close the stream. However, now I’m working on a program in which I want to keep a FileStream open in order to allow the user to retain access to the file while they are working in between saves. ( See my previous question).

I’m using XmlSerializer to serialize my classes to a from and XML file. But now I’m keeping the FileStream open to be used to save (reserialized) my class instance later. Are there any special considerations I need to make if I’m reusing the same File Stream over and over again, versus using a new file stream? Do I need to reset the stream to the beginning between saves? If a later save is smaller in size than the previous save will the FileStream leave the remainder bytes from the old file, and thus create a corrupted file? Do I need to do something to clear the file so it will behave as if I’m writing an entirely new file each time?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Your suspicion is correct – if you reset the position of an open file stream and write content that’s smaller than what’s already in the file, it will leave trailing data and result in a corrupt file (depending on your definition of “corrupt”, of course).

    If you want to overwrite the file, you really should close the stream when you’re finished with it and create a new stream when you’re ready to re-save.

    I notice from your linked question that you are holding the file open in order to prevent other users from writing to it at the same time. This probably wouldn’t be my choice, but if you are going to do that, then I think you can “clear” the file by invoking stream.SetLength(0) between successive saves.

    • 0