Applied XML Programming for Microsoft .NET.pdf - Csbdu.in

typeof(ServiceSalesProvider),"tcp://192.345.34.1:8082");You can also direct the caller application to read setup information from a configurationfile located in the same path as the executable. In this case, the convention is to givethe file the same name as the executable plus a .config extension. You then pass thefile name to the Configure method, as shown here:RemotingConfiguration.Configure("MyClient.exe.config");The following script shows the layout of a client configurationfile:As you can see, the differences between the client and the server-side configurationfiles are minimal and are all related to the use of the tag instead of .The server object publishes the list of supported channels, and based on that list, theclient can decide which channel to use. Note that servers must register at least onechannel. Clients are not required to indicate a channel. If a client doesn't indicate achannel, the .NET Remoting system uses one of the default channels. On the otherhand, a client that plans to use a given channel must first register with it. Theapplication can run the channel registration procedure personally or let it run by defaultunder the control of the RemotingConfiguration object.Channels are registered on a per-AppDomain basis and must have unique names inthat context. On physical machines, however, only one channel can listen to a givenport. In other words, at any time you can't have more than one channel registered towork on a given port on a given machine.A client enabled to make remote calls on a remote object simply creates an instance ofthe desired class using the language-specific operator for instantiation—new in C# andVisual Basic. Alternatively, the client can use the System.Activator object—a managedcounterpart of the VBScript CreateObject and GetObject functions.448