V
VJ
Our application writes pretty large XML files to local file store.. I would
say anywhere between 3-5MB of data at time.. but nothing more...The
DataSet.WriteXML() method in the framework, corrupts the files when System
is shutting down. What I mean here is the file does not get flushed
properly, I see a corrupted XML file written. So if the system shutdown has
started how do I prevent the DataSet file being not written. I have tried to
prevent this from happening by making sure that, I create a back file and
only the new file if there is a success of creating a back up. After I
successfully create the new file then I delete the backup to keep the
original. Some how 3 out 10 times in testing, I get both my backup and the
original file corrupted.
I also know that when shutdown beings the .NET domain unloads and commands
get executed. But if that is the case, why is the Write XML being corrupted?
Can't the WriteXML not flush the file or do something to write the full file
or nothing. Is there a known bug? We do have a mechanism for databack up in
our system. But Sometimes, when system shutdowns and if our application is
performing a operation that has sequences of commands that write to both
original and backup, then both locations get messed up. I guess it almost
comes down to the point that I should write to both locations in way that
the .NET domain or the CLR does not execute these commands on shutdown or
unload. Anybody experience such problems with .NET and have implemented a
solution?
Thanks
Vijay
say anywhere between 3-5MB of data at time.. but nothing more...The
DataSet.WriteXML() method in the framework, corrupts the files when System
is shutting down. What I mean here is the file does not get flushed
properly, I see a corrupted XML file written. So if the system shutdown has
started how do I prevent the DataSet file being not written. I have tried to
prevent this from happening by making sure that, I create a back file and
only the new file if there is a success of creating a back up. After I
successfully create the new file then I delete the backup to keep the
original. Some how 3 out 10 times in testing, I get both my backup and the
original file corrupted.
I also know that when shutdown beings the .NET domain unloads and commands
get executed. But if that is the case, why is the Write XML being corrupted?
Can't the WriteXML not flush the file or do something to write the full file
or nothing. Is there a known bug? We do have a mechanism for databack up in
our system. But Sometimes, when system shutdowns and if our application is
performing a operation that has sequences of commands that write to both
original and backup, then both locations get messed up. I guess it almost
comes down to the point that I should write to both locations in way that
the .NET domain or the CLR does not execute these commands on shutdown or
unload. Anybody experience such problems with .NET and have implemented a
solution?
Thanks
Vijay
