[Mono-bugs] [Bug 82497][Maj] Changed - Verifier ignores InternalsVisibleTo

[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 kumpera at gmail.com.

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

--- shadow/82497	2007-08-20 21:33:23.000000000 -0400
+++ shadow/82497.tmp.30207	2007-08-21 10:34:31.000000000 -0400
@@ -1,12 +1,12 @@
 Bug#: 82497
 Product: Mono: Runtime
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: REOPENED   
+Status: NEEDINFO   
 Resolution: 
 Severity: Unknown
 Priority: Major
 Component: JIT
 AssignedTo: kumpera at gmail.com                            
 ReportedBy: contact at i-nz.net               
@@ -75,6 +75,36 @@
 	IL_0017:  call unsigned int32 class NDesk.GLib.IO::AddWatch(valuetype
 NDesk.GLib.IOChannel, valuetype NDesk.GLib.IOCondition, class
 NDesk.GLib.IOFunc)
 	IL_001c:  pop 
 	IL_001d:  ret 
     } // end of method BusG::Init
+
+------- Additional Comments From kumpera at gmail.com  2007-08-21 10:34 -------
+Hi Ivan,
+
+I have managed to reproduce your problem building dbus-sharp in a
+non-trivial way. I patched the Makefile of dbus-sharp to call gmcs
+with -d:STRONG_NAME.
+
+This was the only way I found to make it use strong names when
+refering to friend assemblies. The new define will trigger
+dbus-sharp/AssemblyInfo.cs to use the public key of NDesk.DBus.GLib.
+
+The next step was to get NDesk.DBus.GLib built with a public key. But
+I could not make it happen, as neither the Makefiles or the configure
+script have the appropriate support. I could not even find the right
+snk file under f-spot 0.3.5. The same happens for f-spot 0.4.0 and trunk.
+
+I have tested InternalsVisibleTo independent of f-spot and it works.
+What might be happening is that you have a system with incompatibly
+build assemblies. It might be the case that NDesk.DBus is built using
+InternalVisibleTo with a public key and NDesk.DBus.GLib is built
+either without a public key or a diferent one.
+
+You need to check if your assemblies are correctly built and to do
+that you can use pedump on NDesk.DBus.GLib to check for the public key
+and monodis on NDesk.DBus to check the custom attribute
+InternalsVisibleTo for a PublicKey part. You could just attach the
+output of these commands to this bug report.
+
+