Enable LinqPad to release its lock on a referenced DLL
Any referenced DLLs cannot be overwritten by another application (Visual Studio in this case) when LinqPad has referenced them and the query has been executed at least once. The query window has to be closed and reopened for the file to be overwritten.
Rowan
shared this idea
Completed in 4.37. By default LINQPad now shadows DLLs referenced into memory.
-
joe
commented
seems to be doing it again in v4.41.02
after running a query using a referenced dll from My Extensions, the dll cannot be overwritten or deleted (it just comes back) -
Jeremy Thomas commented
How can we get a Custom Typed Data Context Driver to shadows referenced DLLs?
I.e. using when I use the UniversalStaticDriver in your DataContextDriverDemo with a LINQtoSQL dll it isn't shadowed but when I use the built-in LINQtoSQLTyped Data Context Driver it is.
(using 2.38.01) -
Joe P
commented
Also, version 4.37 still seems to be locking the file (over a network).
-
Joe P
commented
Will it grab a NEW reference to the DLL each time the query is run (for instance, if the DLL gets updated between query runs)? If not, then it's sort of a bug...
-
Rowan
commented
Seems to have fixed the problem. Thanks a mil.