umm.... Do you mean that your remoting configuration is in the form of
<add key=... /> statements?

In that case, I think you are out on a wild goose-chase :)

Here is an example of a remoting section that exposes single-use objects,
that I use in a web.config:

   <system.runtime.remoting>
   <application>
     <channels>
        <channel ref="http">
          <serverProviders>
            <formatter ref="binary" />
          </serverProviders>
        </channel>
     </channels>
     <service>
       <wellknown mode="SingleCall" type="Service.SecurityService,
Service.SecurityServices" objectUri="SecurityService.soap" />
       <wellknown mode="SingleCall"
type="Service.UserAdministrationService,
Service.UserAdministrationServices"
objectUri="UserAdministrationService.soap" />
       <wellknown mode="SingleCall" type="Service.SearchService,
Service.SearchServices" objectUri="SearchService.soap" />
       <wellknown mode="SingleCall" type="Service.InformationCardService,
Service.InformationCardServices" objectUri="InformationCardService.soap"
/>
       <wellknown mode="SingleCall" type="Service.InquiryService,
Service.InquiryServices" objectUri="InquiryService.soap" />
     </service>
   </application>
  </system.runtime.remoting>

There is a very specific syntax to use - I recommend you pick up Ingo
Rammers excellent book: Advanced .Net remoting - it will give you the
easiest entry into remoting.

-Inge

On Thu, 6 Mar 2003, Dave Thorson wrote:

> I've included my 'remoting' configuration settings in an appSettings block
> in the app.config file then read them in via the standard
> ConfigurationSettings.AppSettings. ie.
>
> <add key="namespace.type"  value="http://localhost/virtdir/factory.rem"; />
>
> Granted the settings I have only represent the wellknown types of the SAO.
> The key value pair represents the setting you would normally be put under
> the <client><wellknown> blocks.  When activating the key is cast as the
> appropriate type, in my instances an Interface defined in a shared assembly.
>
> Of course you still have to have a security policy on the users machine but
> chances are that your application will need that anyway being a rich client.
>
> Dave Thorson
>
> ===================================
> 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
>

===================================
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

Reply via email to