Databases
StackOverflow2013
Postsdbo
POXMLSerializers Dll Loading Fails with Assembly.Load(byte[] asm)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POXMLSerializers Dll Loading Fails with Assembly.Load(byte[] asm)
    primarykey
    data
    text
    <p>I have a strange situation in regards to xml serialization...</p> <p>If I run MyApp.exe (.NET 2.0 WinForms app) with properly generated MyApp.XMLSerializers.dll all is well and the serialization is fast (no serialization assemblies are generated at runtime, because serializers dll is found and is behaving).</p> <p>Now, if I embed MyApp.exe as a resource in MyOtherManagedApp.exe (also .net 2.0) and execute the original app from inside as follows...</p> <pre><code>pasm = System.Reflection.Assembly.Load(MyOtherManagedApp.Properties.Resources.MyAppExeBinary); Type type = pasm.GetType("MyApp.MyModule"); type.InvokeMember("Main", BindingFlags.Default | BindingFlags.InvokeMethod | BindingFlags.Static | BindingFlags.NonPublic, null, null, new object[] {args}); </code></pre> <p>... the original app loads and runs just fine, except for serialization part:</p> <ol> <li><p>If MyApp.XMLSerializers.dll is present in the working directory of MyOtherManagedApp, I get an error stating that MyApp.exe assembly cannot be found (the error is thrown by autogenerated MyApp.XMLSerializers.dll which for some strange reason, inspite of the fact that not only MyApp assembly has been loaded but is in fact executing, fails to find it).</p></li> <li><p>If MyApp.XMLSerializers.dll is NOT present in the working directory, no errors occur, but serialization assemblies are now being generated at run time which result in a big performance hit.</p></li> </ol> <p>So, my question is why does it not work as it should? Namely, why MyApp.XMLSerializers.dll works perfectly if the serialization is started by MyApp.exe when it's running by itself; whereas if it was started via Assembly.Load and InvokeMember from a different assembly, MyApp.XMLSerializers.dll complaints that it cannot find the very same MyApp assembly which has been dynamically loaded and is now running?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFit Dev
    1. USFit Dev
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POXMLSerializers Dll Loading Fails with Assembly.Load(byte[] asm)
      1. USpmartin
      1. VTFavorite
    2. VO
      singulars
      1. POXMLSerializers Dll Loading Fails with Assembly.Load(byte[] asm)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POXMLSerializers Dll Loading Fails with Assembly.Load(byte[] asm)
      1. USRest Wing
      1. VTFavorite
    1. COI am suspecting it may have to do with the 3 contexts into which assemblies can be loaded. My suspicion is that if assembly is loaded from a byte array, as the documentation says it will be loaded into a different context than the main app, and hence maybe it does not properly detect the serializers assembly?
      singulars
      1. POXMLSerializers Dll Loading Fails with Assembly.Load(byte[] asm)
      1. USFit Dev
    2. COSounds like a circular dependency to me. It is probably trying to load an old version of your .exe and fails. You can see it with fuslogvw.exe, finding the type in the .exe that you serialization assembly needs can be it bit more difficult. Build + Clean and build only your assembly.
      singulars
      1. POXMLSerializers Dll Loading Fails with Assembly.Load(byte[] asm)
      1. USHans Passant
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload