title: C# File.Replace protecting against a crash
body: <p>Does <code>File.Replace</code> do an atomic/transactional operation such that if there is a crash or power failure the destination file will never be missing nor a partial file (i.e. will be the original or the new file)?</p>
  
  <p>If not, is there another method that would protect against this scenario?</p>
  
  <p>Note: This would be on an NTFS drive with Windows 7 or later, which I understand supports transactions.</p>
  
  <p>Note: I am asking about saving in an atomic manor and not concerned about a separate process also having the file open like <a href="https://stackoverflow.com/questions/8958094/reliable-file-saving-file-replace-in-a-busy-environment">this question</a>.</p>