Try/catch does not show correct message

Question

Guys, I have a C# code that has the code:

Uri resultadoURL;
bool resultado = Uri.TryCreate(Configuracoes.Configuracao.URL, UriKind.Absolute, out resultadoURL) && resultadoURL.Scheme == Uri.UriSchemeHttp;

if (!resultado)
    throw new Exception(String.Format("URL '{0}' não é válida!", Configuracoes.Configuracao.URL));

On Try/catch, the ex. Message, instead of showing "URL 'xxx' is not valid", is showing the message "Message an exception was triggered by the destination of a call".

Block of Try/catch

catch (Exception ex)
{
    try
    {
        Send(state.State, ToJson(new ResultadoDaIntegracao(false, ex.Message, null)));
    }
    catch { }
}

Does anyone know why the ex. Message comes different?

Answer 1

I found the problem/solution.

As the project is composed of several DLL’s, calling one of these DLL’s, the error presented by eg. Message is from the source process, so it shows the message "Message an exception was triggered by the destination of a call".

The error I needed to show was the error that occurred within the DLL that was called.

For this I used the Innerexception property, which is the Exception error message generated within the destination.

The source was like this:

catch (Exception ex)
{
    try
    {
        if (ex.InnerException != null)
            Send(state.State, ToJson(new ResultadoDaIntegracao(false, ex.InnerException.Message, null)));
        else
            Send(state.State, ToJson(new ResultadoDaIntegracao(false, ex.Message, null)));
    }
    catch { }
}

Answer 2

Simulating his example Marlon Tiedt, I found that it worked:

Note: I made the mistake by writing errorURL.

try
{
    Uri resultadoURL;
    bool resultado = Uri.TryCreate("errorURL", UriKind.Absolute, out resultadoURL) && resultadoURL.Scheme == Uri.UriSchemeHttp;
    if (!resultado)
    {
        throw new Exception(String.Format("URL '{0}' não é válida!", "errorURL"));
    }
}
catch (Exception ex)
{
    try
    {
        var e = ex;
    }
    catch { }
}

Answer 3

Because you did not assign a value to it. There is the internal error (which has no specificity pq is standard). Try setting an Exception and the empty catch and pass the value of the message that returns in 'e' to 'ex'.