Last post Nov 20, 2017 06:14 AM by Fei Han - MSFT
Nov 18, 2017 04:24 AM|rkrex|LINK
What is the best practice for handling website crashes during a CRUD operation. Thanks !
Nov 18, 2017 09:02 AM|PatriceSc|LINK
This is a diagnosis or a design question ? Assuming the later a common approach is to wrap multiple changes inside a single transaction. It allows to do all changes or no change at all. If using Entity Framework it is done for you already by SaveChanges.
If you meant fixing a crash, you should first gather as much information as you can '(know sources being your logging system, the Windows event log or tracing failing requests at the IIS level and in some rare casses could go to taking a crash dump with
Or please be more explicit if it doesn't help.
Nov 18, 2017 09:49 PM|rkrex|LINK
Thank You for your help. I should have been more specific but this is as you were explaining a design issue. I was wondering what if i wanted to save data that a user may have had inputted in form fields. So that if there is a crash when they log back in
Nov 20, 2017 06:14 AM|Fei Han - MSFT|LINK
As PatriceSc said, normally logs can help us troubleshoot IIS or application issues, you can try to enable IIS and application logs
to gather useful logs. This article explain
how to troubleshoot IIS and ASP.NET errors viadiagnosing logs, please refer to it.
If you want to persist data that user entered before, as you mentioned, maintaining user inputs in cookie could be an approach.
If possible, you can also try other approaches, such as