Catastrophic Failure!
-
I am using this message in one of my applications for things that should never happen (but you never know what may happen with Windows), but I guard against anyways. I also include a 'Guru Meditation GUID' so I can find where the issue happened and try and debug it. An example issue: I put a service in a service manager (that uses Unity IoC Container) and get it out a few lines later. If the service is, for some strange reason, not there, I show a message and terminate the application, as something major went haywire.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
I am using this message in one of my applications for things that should never happen (but you never know what may happen with Windows), but I guard against anyways. I also include a 'Guru Meditation GUID' so I can find where the issue happened and try and debug it. An example issue: I put a service in a service manager (that uses Unity IoC Container) and get it out a few lines later. If the service is, for some strange reason, not there, I show a message and terminate the application, as something major went haywire.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
Uh huh. Examples?
-
I am using this message in one of my applications for things that should never happen (but you never know what may happen with Windows), but I guard against anyways. I also include a 'Guru Meditation GUID' so I can find where the issue happened and try and debug it. An example issue: I put a service in a service manager (that uses Unity IoC Container) and get it out a few lines later. If the service is, for some strange reason, not there, I show a message and terminate the application, as something major went haywire.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
...haven't done it since college but I prefer: Program faw down go "Boom!"
-
...haven't done it since college but I prefer: Program faw down go "Boom!"
Certainly if it's going to "faw down", it should "go Boom!"; so many kids nowadays don't think it should "go Boom!". :sigh:
-
...haven't done it since college but I prefer: Program faw down go "Boom!"
I saw that in a Metro App on a friend's computer. :doh: I guess the developer agreed with the Fischer Price comparison.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
I am using this message in one of my applications for things that should never happen (but you never know what may happen with Windows), but I guard against anyways. I also include a 'Guru Meditation GUID' so I can find where the issue happened and try and debug it. An example issue: I put a service in a service manager (that uses Unity IoC Container) and get it out a few lines later. If the service is, for some strange reason, not there, I show a message and terminate the application, as something major went haywire.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
I got "Catastrophic Failure" right from MS: a VB6 app I made years (if not decades) ago, which tries to access a MS Access DB. There was a field with junck in it, making that message.. The same message occured in Access itself, so I believe it's an Access error message.
The signature is in building process.. Please wait...
-
I am using this message in one of my applications for things that should never happen (but you never know what may happen with Windows), but I guard against anyways. I also include a 'Guru Meditation GUID' so I can find where the issue happened and try and debug it. An example issue: I put a service in a service manager (that uses Unity IoC Container) and get it out a few lines later. If the service is, for some strange reason, not there, I show a message and terminate the application, as something major went haywire.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
What about : Welcome to Application suicide booth. Option 5 has been chosen : The user the is too dumb to close the app properly and that's why the application crashed.
Microsoft ... the only place where VARIANT_TRUE != true
LOL! :laugh: :laugh: :laugh: I like to put Easter Eggs in my applications, and I wonder what I should do next.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
What about : Welcome to Application suicide booth. Option 5 has been chosen : The user the is too dumb to close the app properly and that's why the application crashed.
Microsoft ... the only place where VARIANT_TRUE != true
I could use that in some old legacy software. It takes a while to shut down. Despite being told to wait, there are users who will use the task manager to force it to turn off immediately. This causes it to stop in the middle of saving settings to an Access DB which often corrupts the DB. So when the user restarts the program it isn’t happy about having a corrupted DB.
Just because the code works, it doesn't mean that it is good code.
-
I could use that in some old legacy software. It takes a while to shut down. Despite being told to wait, there are users who will use the task manager to force it to turn off immediately. This causes it to stop in the middle of saving settings to an Access DB which often corrupts the DB. So when the user restarts the program it isn’t happy about having a corrupted DB.
Just because the code works, it doesn't mean that it is good code.
just hide the window and let the user think it has shut down. I'm Brazilian; English and other human languages in general aren't my best skills so I apologise for my less than perfect English... "Given the chance I'd rather work smart than work hard." - PHS241 "'Sophisticated platform' typically means 'I have no idea how it works.'"
-
just hide the window and let the user think it has shut down. I'm Brazilian; English and other human languages in general aren't my best skills so I apologise for my less than perfect English... "Given the chance I'd rather work smart than work hard." - PHS241 "'Sophisticated platform' typically means 'I have no idea how it works.'"
We mostly leave the window there so the users won't try to restart it while it is still shutting down. And, yes, they would do this. It really needs a better status report so users don't think it has frozen, but it is old software with no more updates planned.
Just because the code works, it doesn't mean that it is good code.
-
I am using this message in one of my applications for things that should never happen (but you never know what may happen with Windows), but I guard against anyways. I also include a 'Guru Meditation GUID' so I can find where the issue happened and try and debug it. An example issue: I put a service in a service manager (that uses Unity IoC Container) and get it out a few lines later. If the service is, for some strange reason, not there, I show a message and terminate the application, as something major went haywire.
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.