Would you say .Net remoting relies on tight coupling?

Given that both the client and the server need to know everything about the object being remoted, firstly is this tight coupling, and secondly can .Net Remoting wo开发者_运维技巧rk in any other way?

Not really answering your question, but if you want to loosen the coupling, you might look at WCF's NETTCP binding as an alternative. The client can create a proxy for the entities - this way you won't need to share any assemblies (notably Entities) between client and server.