Newly added type can't be resolved #147

New issue

Closed

opened 2013-12-05 23:51:39 -06:00 by johannesegger · 1 comment

johannesegger commented

2013-12-05 23:51:39 -06:00

(Migrated from github.com)

s. http://stackoverflow.com/questions/20386894/importing-a-newly-created-type-into-another-assembly-fails
Caching should be used in all overloads of DefaultAssemblyResolver.Resolve and should also be used when an assembly is read via AssemblyDefinition.ReadAssembly.

s. http://stackoverflow.com/questions/20386894/importing-a-newly-created-type-into-another-assembly-fails Caching should be used in all overloads of `DefaultAssemblyResolver.Resolve` and should also be used when an assembly is read via `AssemblyDefinition.ReadAssembly`.

jbevain commented

2013-12-06 04:32:49 -06:00

(Migrated from github.com)

I disagree the resolver should not be used when you call ReadAssembly. This call explicitly asks to read the assembly from whatever you pass, a filename or a byte[].

The way to achieve this is to create your own resolver which extends the DefaultAssemblyResolver, and to register the assemblies with the resolver.

I disagree the resolver should not be used when you call ReadAssembly. This call explicitly asks to read the assembly from whatever you pass, a filename or a byte[]. The way to achieve this is to create your own resolver which extends the DefaultAssemblyResolver, and to register the assemblies with the resolver.