FileStream resource locking

[GDL]

Hi,

I'm using a FileStream as below:

FileStream fs = new FileStream
(
filePath,
FileMode.Create ,
FileAccess.Writ e,
FileShare.None
);

//do some writing
fs.Write(...)

//close
fs.Close();

My problem is that even after the stream is closed no other applications can
access the file (resource in use) until I close the application which created
it.

Can anybody help with this please?

--
Many Thanks

[Jon Skeet [C# MVP]]

GDL <GD*@discussion s.microsoft.com > wrote:

I'm using a FileStream as below:

FileStream fs = new FileStream
(
filePath,
FileMode.Create ,
FileAccess.Writ e,
FileShare.None
);

//do some writing
fs.Write(...)

//close
fs.Close();

My problem is that even after the stream is closed no other applications can
access the file (resource in use) until I close the application which created
it.

Can anybody help with this please?

Given the code above, it's possible for an exception to occur and the
file handle not to be closed. A using statement would sort this:

using (FileStream fs = new FileStream (...))
{
// Do the writing
fs.Write (...);

// No need to manually close
}

If exceptions aren't occurring, that shouldn't be the problem, but the
above is better practice anyway.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[GDL]

Hi Jon,

The code snippet is actually wrapped in try / catch blocks in the
application and I'm happy that exceptions are not occuring, also the file
written by the statement is correctly formatted.

I will restructure as per your suggestion for better practice but do you
have any other thoughts as to why the file is remaining locked? I have
similar code in various places throught the application and they all exhibit
the same problem.
--

"GDL" wrote:

Hi,

I'm using a FileStream as below:

FileStream fs = new FileStream
(
filePath,
FileMode.Create ,
FileAccess.Writ e,
FileShare.None
);

//do some writing
fs.Write(...)

//close
fs.Close();

My problem is that even after the stream is closed no other applications can
access the file (resource in use) until I close the application which created
it.

Can anybody help with this please?

--
Many Thanks

[Jon Skeet [C# MVP]]

GDL <GD*@discussion s.microsoft.com > wrote:

The code snippet is actually wrapped in try / catch blocks in the
application and I'm happy that exceptions are not occuring, also the file
written by the statement is correctly formatted.

I will restructure as per your suggestion for better practice but do you
have any other thoughts as to why the file is remaining locked? I have
similar code in various places throught the application and they all exhibit
the same problem.

Nothing else immediately comes to mind.

Could you post a short but complete program which demonstrates the
problem?

See http://www.pobox.com/~skeet/csharp/complete.html for details of
what I mean by that.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[GDL]

Jon,

I've done some more investigation and the problem seems to be time related -
if I wait for what seems to be a variable amount of time but typically
several 10's of minutes then the locks are released - does this point to
garbage collection issues relating to the underlying file handles?

--

"Jon Skeet [C# MVP]" wrote:

GDL <GD*@discussion s.microsoft.com > wrote:

The code snippet is actually wrapped in try / catch blocks in the
application and I'm happy that exceptions are not occuring, also the file
written by the statement is correctly formatted.

I will restructure as per your suggestion for better practice but do you
have any other thoughts as to why the file is remaining locked? I have
similar code in various places throught the application and they all exhibit
the same problem.

Nothing else immediately comes to mind.

Could you post a short but complete program which demonstrates the
problem?

See http://www.pobox.com/~skeet/csharp/complete.html for details of
what I mean by that.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

GDL <GD*@discussion s.microsoft.com > wrote:

I've done some more investigation and the problem seems to be time related -
if I wait for what seems to be a variable amount of time but typically
several 10's of minutes then the locks are released - does this point to
garbage collection issues relating to the underlying file handles?

Yes - it suggests that somewhere, you're opening a FileStream and not
closing it.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too