StrongNamer will hold a lock on files if resolved through the StrongNamerAssemblyResolver.cs.

[Jeff Dammeyer]

Hello,

I encountered an issue today where, in MSBuild only, the StrongNamer package seemed to keep a reference to multiple dlls long after the strong naming was finished.

I think I identified the problematic code in StrongNamerAssemblyResolver.cs

The implementation of dispose is a 'new' method rather than an override, so when it's disposed via the using in the StrongNamer class, those assemblies will never actually be released (since only the base class dispose method will be called.)

Thanks!