Summary
In this chapter, you examined how to configure distinct .NET assemblies to share types between application boundaries. As you have seen, a remote object may be configured as an MBV or MBR type. This choice ultimately controls how a remote type is realized in the client’s application domain (a copy or transparent proxy).
If you have configured a type to function as an MBR entity, you are suddenly faced with a number of related choices (WKO versus CAO, single call versus singleton, and so forth), each of which was addressed during this chapter. As well, you examined the process of tracking the lifetime of a remote object via the use of leases and lease sponsorship. Finally, you revisited of the role of the .NET delegate type to understand how to asynchronously invoke a remote method (which, as luck would have it, is identical to the process of asynchronously invoking a local type).
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 Andrew Troelsen
About this chapter
Cite this chapter
(2005). The .NET Remoting Layer. In: Pro C# 2005 and the .NET 2.0 Platform. Apress. https://doi.org/10.1007/978-1-4302-0060-4_18
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0060-4_18
Publisher Name: Apress
Print ISBN: 978-1-59059-419-3
Online ISBN: 978-1-4302-0060-4
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books