Copy with Overwrite is a safer suggestion (#4295)

merarischroeder · web-flow · commit c2805bef6ecc · 2020-10-29T06:03:52.000-07:00
Added in advice to use Copy with Overwrite in all .Net versions then Delete, rather than Deleting the destination file then Moving.

(Ignore the other patch. I mucked it up.)
diff --git a/xml/System.IO/File.xml b/xml/System.IO/File.xml
@@ -2502,6 +2502,8 @@ Note that if you attempt to replace a file by moving a file of the same name int
 
 - In .NET Core 3.0 and later versions, you can call <xref:System.IO.File.Move(System.String,System.String,System.Boolean)> setting the parameter `overwrite` to `true`, which will replace the file if it exists.
 
+- In all .NET versions, you can call <xref:System.IO.File.Copy(System.String, System.String, System.Boolean)> to copy with overwrite, then call `Delete` to remove the excess source file. This strategy is advisable if the file being copied is small, and you are looking for an "atomic" file operation. If you `Delete` the file first, and the system or program crashes, the destination file will no longer exist. 
+
 - In all .NET versions, you can call <xref:System.IO.File.Delete(System.String)> before calling `Move`, which will only delete the file if it exists.
 
 The `sourceFileName` and `destFileName` arguments can include relative or absolute path information. Relative path information is interpreted as relative to the current working directory. To obtain the current working directory, see <xref:System.IO.Directory.GetCurrentDirectory%2A>.
