Bug 893 - SerializationException when calling a proxy in another AppDomain (Couldn't find assembly 'System')
Summary: SerializationException when calling a proxy in another AppDomain (Couldn't fi...
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: Remoting ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2011-09-19 07:41 UTC by andreas.flucke
Modified: 2015-03-20 05:54 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Tescase (sources,assemblies,Exception) zipped (5.22 KB, application/x-zip-compressed)
2011-09-19 07:41 UTC, andreas.flucke
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description andreas.flucke 2011-09-19 07:41:26 UTC
Created attachment 419 [details]
Tescase (sources,assemblies,Exception) zipped

When trying to call an proxy object in a newly created AppDomain this Exception occurs (see Exception.txt).
The "Callee.dll" assembly is loaded via byte-array into the new AppDomain by "Caller.exe" (EnumProxy.cs is Callee and Caller.cs is Caller.exe")
(Callee.dll has to be referenced by Caller.exe)

This happens on Linux (2.10.2) and OSX too.
(Windows and OSX: 2.10.5)


BTW: please review my 47 Novell Mono Bugs
(some may be solved, but others are important like 547274)

511185 - Console.Beep should work even if apptype is set to winexe
511234 - Crash on loading resources with cultureinfo generated by a windows tool
511275 - Actual cursor position in RichTextBox not available in KeyPress event
511280 - RichTextBox not capable of highlight feature
511282 - RichTextBox doesn't support RTF Tab table
511488 - Linebreaks in RichTextBox are inconsistent (and incompatible)
511524 - Scrollevents doesn't appear in WindProc of RichTextBox
511538 - After merging Menus in an MDI application MenuItem changes don't get recognized
511564 - MDI window caption isn't refreshed when changing Text property
511596 - RestoreBounds property wrong for MDI child windows
511645 - Size/Move window menu commands works different (and senseless) for MDI child windows
511658 - MDI list menu doesn't show a separator
512128 - Scrolling a Listbox actualizes only bottom (or top) lines, not all
512136 - Horizontal scrolling of ListBoxes leads to crippled text
512206 - Cursor property for MDI child window gets resetted
512348 - MDI child window menus sometimes keep alive after closing the child (zombie)
512530 - AltGr keys are captured by menu instead of RichTextBox
512537 - ToolWindow without Text and ControlBox as child window should have no titlebar
512557 - RichTextBox RTF parsing error
512985 - Tooltips not working for MDI childform embedded Controls
513016 - Control remains invisible after reordering form controls
513030 - Copy and Paste in RichTextBox leads to unreadable overwritten text
536557 - ToolboxItem don't has build-in Bitmap
537604 - DragDrop on DesignSurface doesn't seem to work
547274 - Background of controls isn't repainted after disposing them
547516 - Folderbrowserdialog (and others) don't allow to browse the computer
547627 - MDI child windows unusable due to missing background painting
548111 - Double window frame for FormBorderStyle = FixedToolWindow
557713 - Invalid mouse location in MouseMove event when mouse is captured
558724 - Form Scrollbars not visible after AdjustFormScrollbars(true)
558882 - Wrong cursor shape for Cursors.SizeAll
567330 - OpenFileDialog size sorting is wrong
567331 - ToolStrip BackColor property ignored
568862 - ToolStripComboBox doesn't show ToolTipText
575731 - Invalid RichTextBox paste behavior
578401 - Process.MainWindowHandle not supported
588313 - ArgumentOutOfRangeException when accessing RichTextBox.Lines property
591783 - System.ArgumentOutOfRangeException when editing in RichTextBox
641321 - Regression: Thread.CurrentUICulture returns wrong culture
664810 - Opening a WinForm leads to Segmentation Fault (Runtime Crash)
664812 - WinForm Samples crash on Windows
665953 - [Regression 2.10 RC1] Several crashes when trying to start WinForm applications
673611 - [Regression] TreeView nearly unusable, incredible bad performance
674638 - [2.10RC2]: Softdebugger disconnects on AppDomainUnload
677257 - Missing ArgumentException when creating invalid Fonts leads to GDI+ crash
684896 - FontDialog shows invalid Fonts
684898 - Softdebugger for Windows shows Finalizer Thread
Comment 1 Zoltan Varga 2011-09-27 15:37:26 UTC
This happens because the serialization code ends up calling
		AppDomain.CurrentDomain.Load ("System");
which doesn't work in MS.NET either.
Comment 2 andreas.flucke 2011-09-28 02:12:24 UTC
No, this code definitely works in MS.Net (i'm using it).
(And it should work, because a loaded assembly should resolve/load the assemblies it depends on.)
Comment 3 Zoltan Varga 2011-09-28 08:02:16 UTC
I meant the AppDomain.CurrentDomain.Load ("System"); line which our serialization code ends up calling.
Comment 4 Marek Safar 2015-03-20 05:54:36 UTC
Fixed in master