KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I've found several C# application crashes in response to error conditions such as obj = null or obj.member = null . A lot of time, the obj from the interface of 3rdPartyApp. And caused both 3rdPartyApp and MyCsApp crashed together. How could I add exception handling in all possible areas so that my application can survive in these disastrous situations? It is a challenge to add try-catch to ALL places, and recover from the situation. How could I accomplish this in a way which is realistic, reliable and bullet-proof? [Update: Industry Automation Control] Structure: GUI(asp.net, c++) - RuntimeApp (C++) - MyCsApp(cs) - 3rdPartyApp(Cs) Normal procedure: HostApp --(Connect through ethernet Cabele)-- MyCsApp Operator -- GUI -- RuntimeApp -- MyCsApp Abnormal conditions: Some non-standard operation procedure; some hardware issue occurred; etc. I'd better handle all the abnormall conditions. And most importantly, I must think how to recover from the situations.
Tags (comma-separated)
Save Edits
Cancel