Hi Experts!
I have created a compact framework library that contains the core objects. The library should be consumed by both the pocket pc and desktop applications.
However, one of the requirements of the desktop application is that it should utilize .NET remoting. And with the CF .NET 1.1, Serializable attribute isn't supported yet. Are there ways to circumvent this limitation? I thought of creating proxy objects that define SerializableAtt ribute when running in windows app, however this won't solve the problem as proxy objects must contain Serializable objects as well. I really hope to avoid code duplication as much as possible.
Please suggest if you know techniques of using the remoting without the Serializable attribute or any design patterns that I could use.
Thanks in advance!
I have created a compact framework library that contains the core objects. The library should be consumed by both the pocket pc and desktop applications.
However, one of the requirements of the desktop application is that it should utilize .NET remoting. And with the CF .NET 1.1, Serializable attribute isn't supported yet. Are there ways to circumvent this limitation? I thought of creating proxy objects that define SerializableAtt ribute when running in windows app, however this won't solve the problem as proxy objects must contain Serializable objects as well. I really hope to avoid code duplication as much as possible.
Please suggest if you know techniques of using the remoting without the Serializable attribute or any design patterns that I could use.
Thanks in advance!