[Mono-bugs] [Bug 62667][Wis] New - Type.IsSubclassOf behaviour difference

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sat, 7 Aug 2004 11:47:44 -0400 (EDT)

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 colin@breame.com.


--- shadow/62667	2004-08-07 11:47:43.000000000 -0400
+++ shadow/62667.tmp.4046	2004-08-07 11:47:43.000000000 -0400
@@ -0,0 +1,35 @@
+Bug#: 62667
+Product: Mono: Runtime
+Version: unspecified
+OS Details: 
+Status: NEW   
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: colin@breame.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: Type.IsSubclassOf behaviour difference
+Type.IsSubclassOf behaviour is different to the MS platform when the Type
+comes from an assembly that has been loaded using the Assembly.Load method.
+Say the assembly loaded using Assembly.Load contains the class B that
+extends class A which is statically linked in the running program.
+Where t is the type of B in the loaded assembly:
+Calling t.IsSubclassOf(typeof(A))
+  - MS - returns false
+  - mono - returns true
+This is something to do with a loaded assembly becoming isolated from the
+statically linked code in the running program.  As far as I can tell, this
+makes plugins impossible as you can never find out which types are
+available in an assembly, unless I'm missing something (which is probably
+the case), this is stupid.