.NET Remoting Tips and Best Practices


In this chapter, you’ve seen some of the most important best practices for developing .NET Remoting applications. This list is, of course, not complete, but it reflects the most common points I have encountered on consulting projects, and in personal e-mail exchanges with several hundred developers who are using .NET Remoting in their daily projects.

Apart from a detailed look at several scenarios for .NET Remoting, you’ve learned that there are also numerous cases for which remoting is not the right solution. I have briefly introduced you to UDP and MSMQ, which can be used for scalable delivery of asynchronous notifications.

At the end of this chapter, you’ve seen how easy it is to configure a Windows Network Load Balancing cluster, which provides your applications with transparent failover and the possibility to scale out.

In the following chapter, I’ll discuss the most common causes—and solutions—for problems and issues when using .NET Remoting.


Connection Request User Datagram Protocol Enterprise Service Incoming Request Public Class 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Ingo Rammer and Mario Szpuszta 2005

Personalised recommendations