C#

sharpiesharpie wrote:

if you dispose after you close it throws an exception

sharpiesharpie wrote:

fs.Dispose();
fs.Close();

Colin Angus Mackay wrote:

As implemented, Close() calls Dispose() which, in turn, calls Flush()

Scott Dorman wrote:

I just double-checed that through Reflector

public override void Close()
{
      this.Dispose(true);
      GC.nativeSuppressFinalize(this);
}
 
protected virtual void Dispose(bool disposing)
{
      if (this._handleProtector != null)
      {
            if (!this._handleProtector.IsClosed)
            {
                  this.Flush();
            }
            this._handleProtector.Close();
      }
      this._canRead = false;
      this._canWrite = false;
      this._canSeek = false;
      this._buffer = null;
}
 
public override void Flush()
{
      if (this._handleProtector.IsClosed)
      {
            __Error.FileNotOpen();
      }
      if (this._writePos > 0)
      {
            this.FlushWrite();
      }
      else if ((this._readPos < this._readLen) && this.CanSeek)
      {
            this.FlushRead();
      }
}

sharpiesharpie wrote:

err...so...what's the best way to do it? flush + close?

public virtual void Close()
{
    this.Dispose(true);
    GC.SuppressFinalize(this);
}
 
public void Dispose()
{
    this.Close();
}
 
protected virtual void Dispose(bool disposing)
{
    if (disposing && (this._asyncActiveEvent != null))
    {
        this._CloseAsyncActiveEvent(Interlocked.Decrement(ref this._asyncActiveCount));
    }
}

public override void Flush()
{
    if (this._handle.IsClosed)
    {
        __Error.FileNotOpen();
    }
    if (this._writePos > 0)
    {
        this.FlushWrite(false);
    }
    else if ((this._readPos < this._readLen) && this.CanSeek)
    {
        this.FlushRead();
    }
}