I want to copy a folder, and i want to delete destination folder first. So I am deleting destination folder then recreate it and then copy files. The problem is that i get the <
Why are you setting the file attributes after you have copied the file? Is this necessary?
What you could do is first setting the the different attributes and afterwards doing the actual file copy. It also makes more sense, first checking if it is a ReadOnly file, and if it is, then set it to Normal, and do the copy.
Sorry for answering and not commenting but my reputation isn't high enought yet. In the MSDN is written, that the path has to be "well-formed" http://msdn.microsoft.com/en-gb/library/system.io.fileinfo%28v=VS.90%29.aspx
Maybe trying it out, by putting file in the working directory? So no path is needed and you can see if the problem is in the path or in the file...
You got it kinda wrong. The reason for the exception is that there's still a resource that is accessing the folder (or file).
The solution is never GC.collect()
or Sleep()
... That's just a work around.
What you're doing is just letting the garbage collector dispose of the resource, and then giving it time to act.
The RIGHT way is to manage your own resources. Instead of a static method that you have no control on, use a using
block and dispose of the resource in the end of the block. This way there's no overhead while your waiting for things that aren't under your control (GC).
Use an object that controls the resources, and the using
block will dispose it at the end.
In your case, using a single DirectoryInfo
object that controls that resource should work.
Ok This is very strange. the exception only happen when the destination folder is empty. but adding the folowing line after the destination folder deletion seem to solve the problem. the line : MessageBox.Show("folder " + destFolder + "folder was deleted", "alert");
static public void CopyFolder(string sourceFolder, string destFolder)
{
if (Directory.Exists(destFolder)) // check if folder exist
{
Directory.Delete(destFolder, true); // delete folder
MessageBox.Show("folder " + destFolder + "folder was deleted", "alert");
}
Directory.CreateDirectory(destFolder); // create folder
string[] files = Directory.GetFiles(sourceFolder);
foreach (string file in files)
{
string name = Path.GetFileName(file);
string dest = Path.Combine(destFolder, name);
File.Copy(file, dest, true);
FileInfo fileinfo = new FileInfo(dest); // get file attrib
if (fileinfo.Attributes != FileAttributes.ReadOnly) // check if read only
File.SetAttributes(dest, FileAttributes.Normal);
}
so putting a MessageBox.show after the deletion causes the System.IO.DirectoryNotFoundException to go away. its as if the fact that there is a small delay after the deletion , the recreation of the folder goes well. i guess i will find a work around this, but if someone knows what is causing this and the way to solve it , i will be very happy to hear it.
Try to set Fileinfo of dest first, then copy
foreach (string file in files)
{
string name = Path.GetFileName(file);
string dest = Path.Combine(destFolder, name);
FileInfo fileinfo = new FileInfo(dest); // get file attrib
dest.Attributes = FileAttributes.Normal;
File.Copy(file, dest, true);
}.......
Try using the FileIO method instead, I had the same issue, code below works perfect.
FileIO.FileSystem.DeleteDirectory(directoryName,FileIO.DeleteDirectoryOption.DeleteAllContent)