[Mono-devel-list] un-interoperatible classes .NET -> Monoremoting

Anset anset at anset.org
Tue Sep 28 08:18:07 EDT 2004


Hi,

> As an alternative to compatibility problems, you could write two middle
> layers - one for each platform.  MonoLayer will translate to and from a
> Mono implementation to your new common implementation, and MSLayer will
> do the same, but for MS implementations.

I assume these middle layers would "simplify" complex class objects like
array lists to their individual components?
If so, how "low" does one have to go to be guaranteed Mono <-> .Net
interoperability?

Would a string also be guaranteed to work or would one need to use char
arrays?
Only primitive (built-in) types? Only bits and bytes?

Wkr,

Anset




More information about the Mono-devel-list mailing list