Hey,
On Wed, Jan 18, 2012 at 11:24 PM, Ken Beckett <[email protected]> wrote:
> However, while I've often gotten these exceptions, I'm occasionally
> getting a 'null' return from Resolve()! Anyone have any ideas on how
> this can occur?
Some TypeReference can not be resolved into a TypeDefinition.
Trying to Resolve a GenericParameter or a FunctionPointerType for
instance, shouldn't Resolve to anything.
> I'm specifically seeing this when using the
> GlobalAssemblyResolver.Instance as a resolver, like this:
>
> var assemblyResolver =
> (DefaultAssemblyResolver)GlobalAssemblyResolver.Instance;
>
> assemblyResolver.AddSearchDirectory(searchDirectory);
> AssemblyDefinition assembly =
> AssemblyDefinition.ReadAssembly(assemblyFileName, new ReaderParameters
> { AssemblyResolver = assemblyResolver });
That's not really a good idea.
The GlobalAssemblyResolver is going to be removed before 1.0.
But I should save that for the answer about The Terrible Memory Leak.
Jb
--
--
mono-cecil
