Summary

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 that SoapSuds -ia:<input assembly> -nowp -oa:<outputfile.DLL> will generate the necessary metadata 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.

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.

In the next chapter, I show you how you can also use IIS to provide authenticated and encrypted access to your remote components.