http://bugzilla.novell.com/show_bug.cgi?id=617714
http://bugzilla.novell.com/show_bug.cgi?id=617714#c7 --- Comment #7 from Marek Habersack <[email protected]> 2010-06-30 15:54:28 CEST --- Created an attachment (id=372895) --> (http://bugzilla.novell.com/attachment.cgi?id=372895) net_4_0_assembly_remapping_test.tar.bz2 Reopening because the fix isn't complete. While it does fix the original compilation issue, it doesn't fix the runtime behavior. The test case above shows the problem. It contains a 2.0 assembly which references System.Core 3.5 and a 4.0 app which references System.Core 4.0. The app compiles and links fine, but when run it outputs: ---------- Same lock type? False Value for 'key' is 'value' ---------- while the correct output is: ---------- Same lock type? True Value for 'key' is 'value' ---------- The lock type mentioned above is System.Threading.ReaderWriterLockSlim, found in System.Core. It seems the assembly.c diff is, after all, necessary. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
