Loading plug-in DLL files, "The invoked member is not supported in a dynamic assembly."

c# .net-4.0 .net-2.0 .net-assembly dynamic-assemblies
Trevorm picture Trevorm · Apr 10, 2012 · Viewed 25k times · Source

We have custom DLL's that are not included in our initial setup file. They are loaded at runtime. This process worked fine while using .NET 2.0, but we are getting the "The invoked member is not supported in a dynamic assembly" error message now that we are using .NET 4.0.

try
{
    assem = Assembly.LoadFrom(fi.FullName); //fi is FileSystemInfo
}
catch (FileLoadException) {}
catch (BadImageFormatException) {}
catch (System.Security.SecurityException) {}
catch (ArgumentException) {}
catch (PathTooLongException) {}

Answer

Gusdor picture Gusdor · Apr 28, 2017

This error is occurring because Assembly.Load cannot be called upon dynamic assemblies. You must filter out the dynamic assemblies before using them.

var assemblies AppDomain.CurrentDomain.GetAssemblies().Where(p => !p.IsDynamic);

Related questions

"This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded"

I'm getting the error: "This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded." I have a .NET 4.0 dll project that is being called by a .NET 2.0 project. Is there a way to …

Read More
.net construct for while loop with timeout

I commonly employ a while loop that continues to try some operation until either the operation succeeds or a timeout has elapsed: bool success = false int elapsed = 0 while( ( !success ) && ( elapsed < 10000 ) ) { Thread.sleep( 1000 ); elapsed += 1000; success = ... some operation ... } I …

Read More
Mixed mode assembly is built against 'v2.0.50727' error

First of all, I've found the other posts on StackOverflow here, but it did not resolve my error. I have 3 different environments/domains with a build server in each location. My Dev and UAT environments build just fine, but the …

Read More