Dynamic proxy uses static assembly names for generation of proxy types. This is very much needed when it comes to strong naming assemblies and declaring friend assemblies. The trouble is you cannot control what hosting processes(or consumers of Castle DP) do.
A file lock on "CastleDynProxy2.dll" via a test run in Resharper, will cause an I/O collision when running tests via the console.
Is there perhaps a way of creating a "bottom up" way of revealing this?