Home
Options

Why is LINQPad directly referencing (and locking) my assemblies

I added some references to my assemblies in My Extensions, so they're automatically available to all queries. "Do not shadow assembly references" is false - I never changed it. After I run some stuff in LINQPad I cannot rebuild my assemblies in Visual Studio - the files are in use. Using Process Hacker I can see that they're open by LINQPad.UserQuery.exe (handle types File, Section and Mapped Image). I can reproduce this every time.

On occasion I've even seen some assemblies opened by LINQPad.exe, though I cannot reproduce that.

Why is this happening and how do I stop it? I want to be able to rebuild my assemblies easily.

Comments

Sign In or Register to comment.