I understand that .NET FileStream\'s Flush method only writes the current buffer to disk, but dependent on Windows\' disk driver and the hard disk firmware this is no guaran
There's simply too many levels of abstraction to be absolutely sure that the data is written to the disc, right down to the hardware level.
Not brilliantly performant or foolproof, but how about re-opening the file once it is written in a seperate process and checking the size or contents?