Using FileStream or not?

[morph276]

Which is better to use, FileStream or File.Create?

[Barry Kelly]

mo******@yahoo.com wrote:

Which is better to use, FileStream or File.Create?

File.Create uses FileStream. File acts as a neat starting point for lots
of file routines, so it can make code easier to read. In particular, if
you use File.Create you don't have to specify the right file mode etc.

If the use case you need is handled by one of the File methods like
File.Open / File.Create / File.CreateText etc., I'd advise using it,
because it ends up being more readable.

-- Barry

--
http://barrkel.blogspot.com/

[William Stacey [MVP]]

The second still returns a FileStream. Just a static helper method for a
FileStream constructor. Myself, I using the FileStream, so the FileMode,
FileAccess and FileShare are explicitly documented in my code at a glance.

File.Create is a static helper:
public static FileStream Create(string path, int bufferSize, FileOptions
options)
{
return new FileStream(path, FileMode.Create, FileAccess.ReadWrite,
FileShare.None, bufferSize, options);
}

--
William Stacey [MVP]

<mo******@yahoo.comwrote in message
news:44***********************@fe4.nntpserver.com. ..
| Which is better to use, FileStream or File.Create?

[Arne Vajhøj]

mo******@yahoo.com wrote:

Which is better to use, FileStream or File.Create?

No functional difference.

I like the constructor because of its OO style.

The other is bit VBS'ish.

But that is just my personal taste.

Arne