[Mono-list] Re: Remoting (ping Rob Jordan)

Robert Jordan robertj at gmx.net
Tue Oct 18 07:32:32 EDT 2005

Hi Peter,

> I'm following up on the business of the customErrors element in remoting
> server exe.config files: specifically whether or not the first character
> of the mode attribute value should be capitalised or not.
> I'm in work at the  moment where I've confirmed what I said last night -
> i.e. that the first character must be capitalised for custom errors to
> work.  We fell foul of this here and did extensive testing to show that
> the capital letter was required.  My hesitancy last night was simply
> that I wanted to confirm to my own satisfaction that I hadn't remembered
> things back-to-front.
> The problem is the Microsoft documentation.  Sometimes they use a
> capital
> (http://www.microsoft.com/technet/prodtechnol/speech/library/mss/sas_adm
> _mon_view_remote.mspx and
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_jlca
> /html/vberr2005globalerrorwebconfigcustomerrorsmodepropertymustbesettoon
> .asp for example) and sometimes they don't
> (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenr
> ef/html/gnconcustomerrorselement.asp).  Unfortunately, this last example
> is the main reference for the element: but it's wrong.  The capital
> letter is needed.

The docs might be ambiguous (ASP.NET has this element as well).
However, I don't understand why on earth they are not parsing these
settings while reading the config file (like mono does) and throw
some exception if the settings were wrong.

> Hope this helps - and if you want me to write a test application to
> prove the point, I'll do that for you.  Just ask.

It has been fixed:


Mono is now case insensitive.


More information about the Mono-list mailing list