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 [EMAIL PROTECTED]

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

--- shadow/59665        2005-05-06 18:49:17.000000000 -0400
+++ shadow/59665.tmp.4782       2007-08-03 18:07:56.000000000 -0400
@@ -100,6 +100,30 @@
 
 ------- Additional Comments From [EMAIL PROTECTED]  2005-01-15 17:41 -------
 *** Bug 71302 has been marked as a duplicate of this bug. ***
 
 ------- Additional Comments From [EMAIL PROTECTED]  2005-05-06 18:49 -------
 *** Bug 71299 has been marked as a duplicate of this bug. ***
+
+------- Additional Comments From [EMAIL PROTECTED]  2007-08-03 18:07 -------
+Some info on how the GUID is generated:
+http://blogs.msdn.com/adam_nathan/archive/2003/10/19/56779.aspx
+
+Relevant section:
+
+The goal of the GUID-generation algorithm is to change GUIDs when
+incompatible changes are made to managed types, but to keep them
+unchanged when compatible changes are made.
+
+Here's how it works:
+
+    *
+      CLSIDs (and GUIDs on stucts) are generated based on a hash of
+the fully-qualified class name plus the name, version, and public key
+of the assembly containing the class.
+    *
+      IIDs are generated based on a hash of the fully-qualified
+interface name plus the signatures of all the interface s members that
+are exposed through Interop.
+    *
+      LIBIDs are generated based on a hash of the name, version, and
+public key of the assembly.
_______________________________________________
mono-bugs maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-bugs

Reply via email to