.NET Remoting and the customErrors tag

To continue on my remoting rant.....

We were stilling see strange behaviors when remoting over the WAN.  I finally broke down and called Microsoft.

I sent them my client and server config files.  They said they both were correct, EXCEPT on the server I had added the customErrors=on element.  Why? Because the exception told me to to see more details.  Why again? Because all of the documentation on remoting tells you to in order to see more details on the exception.

Per the MS rep, the docs are written incorrectly.  Our remote server was not throwing an exception.  7 days of debugging only to discover the docs are inccorect.  I changed this value from 'on' to 'off' and now all of our remote methods work.  You have got to be kidding me.....  

Chris Taylor discusses something similar to this here.

07/23/04 UPDATE

customErrors is an attribute in the server's config file that tells the server to propagate the exception back or send mback a general remoting exception.  Its set to “off“ by default, which tells the server to send the real exception back.  Setting it to “on“ tells the server to send a general remoting exception.  Now, where the confusion lies is the dialog box that pops up the first time you see a general remoting exception. It tells you to set customErrors “on“ to see the details.  Well, “on“ really means set the attribute to “off”.