Missing default AssemblyResolver on .NET Core

I have essentially the following program:

var module = ModuleDefinition.ReadModule(moduleName);
var type = module.Types.Single(ti => ti.FullName == typeName);
var method = type.Methods.Single(mi => mi.Name == methodName);
foreach (var instr in method.Body.Instructions) {
    switch (instr.OpCode.Code) {
        case Code.Call: {
            var mref = instr.Operand as MethodReference;
            var mdef = mref.Resolve();
        }
    }
}

This works fine in Mono, but gives an ArgumentNullException running in .NET Core (Linux) when calling mref.Resolve(). Stacktrace is

System.ArgumentNullException : Value cannot be null.
Parameter name: assemblyResolver
   at Mono.Cecil.MetadataResolver..ctor(IAssemblyResolver assemblyResolver)
   at Mono.Cecil.ModuleDefinition.get_MetadataResolver()
   at Mono.Cecil.ModuleDefinition.Resolve(MethodReference method)
   at ...

[jbevain]

Fixed in #444.

[per-samuelsson]

@jbevain

I might be missing something essential here, but I just can’t see how the custom resolver posted earlier could have ever worked.

Basing it on DependencyContext.Default.CompileLibraries, will that not resolve to libraries of the current application? And if so, how often would you want to resolve references based on that?

I’m guessing “all” Cecil consumers would work on a given input assembly, and for that to work, resolving must be based on that, no?

If you’d ever find time to reflect on that, could you also comment on the status of this:

Good catch, we do not have a default assembly resolver for .NET Core. That’s something we need to fix.

(And just to make sure I’m not only coming here bringing pain: I really love Cecil; its code-base, the design, and the straightforwardness in using it - big props! 💘)