Can I replace "throw new exception" with a custom popup?

Question

1.00/5 (2 votes)

See more:

Hi,

Can I replace "throw new Exception" with a custom popup without causing problems in the program?

I want to replace this:

C#

throw new Exception("I show my message.");

with this;

C#

this.Alert("I show my message", FAlert.enmType.Info);

THANKS

What I have tried:

I know it's possible, but I don't know if it will cause any problems or bugs.

Posted 13-Jun-23 1:37am

Anaîs laffont

Updated 13-Jun-23 9:36am

PIEBALDconsult

v2

Add a Solution

Comments

Richard Deeming 13-Jun-23 7:45am

We cannot see your screen, access your computer, or read your mind. There is no way anyone can tell you what impact that change would have on your code, since we have no idea what your code looks like.

CHill60 13-Jun-23 8:20am

You've tagged this as WinForms but Form does not have an Alert method. When you edit your question to actually add some code, be sure to edit the tags with the correct platform as well

[no name] 13-Jun-23 8:26am

Do you want modal or modeless?

PIEBALDconsult 13-Jun-23 14:53pm

And nasal fitment?

2 solutions

Solution 1

If this is Winforms as you tagged, you could try using MessageBox Class (System.Windows.Forms) | Microsoft Learn[^]

If this is web based, then you need to send a HTML / Javascript Alert to the client browser: they cannot see anything that happens on the server and that is where all the C# code will execute.

Posted 13-Jun-23 2:34am

OriginalGriff

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

JudyL_MD · Accepted Answer · 2023-06-13T09:36:00

The big difference between the two is not the way the message is displayed. It's how control flows afterward. The first will immediately (excluding a finally clause) exit the method after the throw and keep propagating that immediate-exit functionality back up the call stack until some method catches the exception. The second ... assuming Alert just displays a message or a notification ... will continue executing in the current method, starting with the next line of code after the Alert call.

Changing how your method exits may have huge side effects throughout your code. First, you must check the current method and see how it will handle executing after whatever state caused the exception. It probably wasn't designed to continue executing. After fixing that method to deal with whatever situation got you into the exception state, you'll have to check each and every one of the calling methods, and determine how you'll need to modify its error handling.