[Mono-bugs] [Bug 79434][Min] Changed - [PATCH] Order of members does not match MS

[bugzilla-daemon at 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 joncham at gmail.com.

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

--- shadow/79434	2007-04-18 10:22:57.000000000 -0400
+++ shadow/79434.tmp.20044	2007-04-18 10:26:25.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 79434
 Product: Mono: Compilers
 Version: 1.0
 OS: unknown
 OS Details: 
-Status: REOPENED   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Minor
 Component: C#
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: joncham at gmail.com               
 QAContact: mono-bugs at ximian.com
@@ -136,6 +136,35 @@
 application built using csc 2.0.
 
 ------- Additional Comments From joncham at gmail.com  2007-04-18 10:22 -------
 Created an attachment (id=19079)
 test.zip - Updated test case
 
+
+------- Additional Comments From joncham at gmail.com  2007-04-18 10:26 -------
+I attached a better test case. Previously I used reflection which I
+stated was not a reliable way to determine order. I have attached a
+test which actually uses COM Interop. Note that things seem to be
+working correctly, i.e. both mono and. Net have the same output.
+
+$ ./test.exe
+Meth1
+Meth2
+Meth3
+PropSet
+PropGet
+
+$ mono test.exe
+Meth1
+Meth2
+Meth3
+PropSet
+PropGet
+
+Thus, this bug is fixed as far as I am concerned since I opened it in
+regards to COM Interop. 
+
+If there is problems with member order dealing with reflection, I
+would open a new bug or ignore as reflection has no guarantee of
+member order (and in fact MS changes it between releases).
+
+