Summary
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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2005 Ingo Rammer and Mario Szpuszta
About this chapter
Cite this chapter
(2005). .NET Remoting Tips and Best Practices. In: Advanced .NET Remoting. Apress. https://doi.org/10.1007/978-1-4302-0011-6_9
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0011-6_9
Publisher Name: Apress
Print ISBN: 978-1-59059-417-9
Online ISBN: 978-1-4302-0011-6
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)