[Mono-bugs] [Bug 72124][Wis] Changed - CultureInfo incompatibilities between Mono 1.1.3 and .NET 1.1.

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by lluis@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=72124

--- shadow/72124	2005-02-02 10:58:50.000000000 -0500
+++ shadow/72124.tmp.15439	2005-02-07 09:39:21.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 72124
 Product: Mono: Runtime
 Version: 1.1
 OS: other
 OS Details: Remoting server: Debian unstable Remoting client:Windows 2003 Server
-Status: NEW   
-Resolution: 
-Severity: 
+Status: RESOLVED   
+Resolution: WONTFIX
+Severity: Unknown
 Priority: Wishlist
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: dezelin32@fastmail.fm               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -34,6 +34,22 @@
 
 
 How often does this happen? 
 Always
 
 Additional Information:
+
+------- Additional Comments From lluis@ximian.com  2005-02-07 09:39 -------
+Mono's CultureInfo is not interoperable with .NET. The problem is that
+.NET's CultureInfo has a private field named m_dataItem which is an
+index to some internal data structures that hold some culture
+information (such as the english name). Mono uses a different
+implementation, and we can't provide that index value.
+
+As a workaround, you can send the culture id to your remote method,
+and construct the culture from it.
+
+In general, when you use remoting, you should avoid sending objects
+whose implementation is not under your control, since object
+serialization relies on the internal structure of objects, and thus it
+is implementation-dependent.
+