I think he was just indicating that he doesn't use static configuration entries to configure his client-side proxies, but rather just calls RemotingServices.Connect directly. The first argument would be the interface type he'd like the proxy to support; and the second parameter (the connection string) would be plucked from his application configuration file. This is a very common approach.
This is all orthogonal to the fact that remoting doesn't work out of the box like web services does when it comes to running in the partially trusted context rich clients run in. -Mike DevelopMentor http://staff.develop.com/woodring > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Inge Stubdal > Sent: Friday, March 07, 2003 1:06 AM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] App.config file not found when > remoting windows app deployed by IIS > > > umm.... Do you mean that your remoting configuration is in the form of > <add key=... /> statements? > =================================== This list is hosted by DevelopMentorŪ http://www.develop.com You may be interested in Guerrilla .NET, 24 March 2003, in London http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
