In this chapter, you learned about the different settings that can be employed in a configuration file. You now also know why configuration files are important and why you shouldn’t hard code the connection information in your .NET Remoting clients.
You know how to use configuration files to allow for transparent use of configuration files for all types of remote objects. I also demonstrated a possible workaround for some problems that you might encounter when using [Serializable] objects in combination with SoapSuds-generated metadata. In the section “What About Interfaces?” in this chapter I also introduced an approach for using configuration files with an interface-based remote object, which eliminates the need for SoapSuds.exe.
I showed you different deployment scenarios, including managed applications such as a console application or a Windows service. You also read about the benefits of using IIS to host your remote objects and how to debug Windows services and IIS as remoting hosts.
In the next chapter, I show you how to build .NET Remoting clients for various technologies: Windows Forms, ASP.NET Web sites, and Web Services.
KeywordsServer Side Configuration File Client Side Attribute Description Visual Studio
Unable to display preview. Download preview PDF.