Mike, With 1.1 even the remoting won't pass along exceptions (or it won't pass along derived exceptions) to the client, you can try it yourself.
To make it work you must add the customErrors tag to the <system.runtime.remoting> section. Chris > -----Original Message----- > From: Mike Woodring (DevelopMentor) [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 25 June 2003 1:11 AM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] remoting exception not > propagating to the client > > > <customErrors> is a web service setting, not a remoting setting. > > Rakesh - are you using remoting or web services? You subject > says remoting, but the description of the error you're seeing > sounds like web services. > > -Mike > DevelopMentor > http://staff.develop.com/woodring > > > > > > -----Original Message----- > > From: Moderated discussion of advanced .NET topics. > > [mailto:[EMAIL PROTECTED] On Behalf Of Chris Day > > Sent: Monday, June 23, 2003 4:25 PM > > To: [EMAIL PROTECTED] > > > > Your .config file should look like > > > > <configuration> > > <system.runtime.remoting> > > <customErrors mode="Off" /> > > >
