ionide-vscode-fsharp icon indicating copy to clipboard operation
ionide-vscode-fsharp copied to clipboard

Published 20 hours ago • verified publisher icon ionide

Ionide locks DLLs even with shadowcopyreferences

Open isaacabraham opened this issue 2 years ago • 3 comments

Describe the bug

Using the --shadowcopyreferences+ should stop locking DLLs when #r is used. However, it appears to still lock them regardless.

Steps to reproduce

  1. Create a .NET DLL.
  2. Reference it from a script.
  3. Rebuild that DLL.

Your rebuild will fail because the DLL is locked.

If you do the same directly with dotnet fsi, the DLL is not locked.

Note, I have indeed added the --shadowcopyreferences+ argument to FSI in VS Code settings and confirmed that it is getting "read" because I also used --nologo and that has taken effect.

isaacabraham avatar Jun 15 '22 17:06 isaacabraham

Do you have FSI Watcher enabled (FSharp.addFsiWatcher)? I can imagine that it can be locking all the assemblies.

Krzysztof-Cieslak avatar Jul 12 '22 12:07 Krzysztof-Cieslak

might also just be an artifact of longer-lived FSI sessions - does it reproduce if you close the FSI session or start a new one before sending the changed file?

baronfel avatar Jul 17 '22 22:07 baronfel

@Krzysztof-Cieslak just checked, no.

isaacabraham avatar Jul 24 '22 19:07 isaacabraham