>When there is an exception, if you mean an unexpected situation, thus an error, usually we go generic on this. As, when this happens, we have no idea on the impact so we log the error and forward the user to a generic page, a page that is not bound on the framework and that will simply tell the user that an unexpected situation happened and that he may click on a given link in that page to return to the main page of the site. We cannot even forward him to the main page because the main page is also inheriting from the framework. So, you need to avoid bouncing the user into an infinite loop. This is why we do it like that.
>
>If this is within a Try/Catch exception, where you control what caused it, then, this means you are still within your application, thus you can offer the user anything you want such as a data entry form to collect data. But, in my experience, we never do that. Most of the data we need is already logged in the Error table.

In my case I'm still in TRY/CATCH block, so I get the exception myself. My problem is that I don't know how to show alert or confirm message when I'm already doing server-side.

Say, if your search returns 0 results, you're somehow showing a messagebox (if I'm not mistaken). I don't know how to do this from the server side.

Showing the info in the label (as it is done now) has a problem - the label text has to be cleared once another action is initiated - and I don't know how to achieve this either.