Hi all,

i've created a module to use some own web methods. Everything is working fine eexcept one thing.

In my method i've created a file:

Dim newFileWriter As IO.FileStream = Nothing
newFileWriter = New IO.FileStream(destFilePath, IO.FileMode.Create, IO.FileAccess.Write)
newFileWriter.Write(bytes, 0, bytes.Length)
newFileWriter.Flush()
newFileWriter.Close()
newFileWriter.Dispose()
newFileWriter = Nothing

This part is working fine.

At the end of my method i want to delete this file:

Dim filename As String = Path.Combine(dataPath, objZipEntry.Name)
If IO.File.Exists(filename) = True Then
 Try
  FileSystemUtils.DeleteFile(filename)
  '// or this version   ->IO.File.Delete(filename)
 Catch ex As Exception
  Return "Could not delete destination File:" + filename + vbCrLf + "error:" + ex.Message
 End Try
End If

On thi part i will get the following error: "The process cannot access the file 'C:\Inetpub\DotNetNuke\Portals\0\DatabaseUploads\ADRESSE.xml' because it is being used by another process."

I don't know where the prodblem ist. Can anybody help ?

I completely agree with Dwayne, if you can avoid dumping to a file in the first place it is your best bet!

However, if you cant here is my experince with this issue. I ran into this same problem a while back working on the IWeb module. It turns out this is more of an issue with IIS than with your code. You can even see this error appear in the DNN file manager window sometimes. I was not able to find any great solution to this problem (nor was anyone else I spoke to about it). So eventually I just decided (and yes I cringe saying this as much as you do reading it) to loop until I was able to delete the file. Typically after a few repeated requests to delete IIS will release the file. The longest running loop I have seen is right around a second.

Let me state very clearly, I am not happy with this solution but it is the best I could come up with and no one could give me a better answer. Your situtaion may be different and you might try doing a scheduled "clean up" process using the DNN scheduler, but that wouldnt work in my case.

the issue is actually not with IIS, but with the ASP.NET file monitor. Actually a delete loop is not such a bad solution...

DNN Blog | Twitter: @erikvb | LinkedIn: