Closed BinToss closed 2 years ago
I'm planning to have HaloSPV3/HXE reference or invoke DeadLock as a library or CLI tool to unlock files in the background.
ERROR_SHARING_VIOLATION
(32): "The process cannot access the file because it is being used by another process".A deadlock .NET library is now available on NuGet. It is awaiting approval but should be available on NuGet soon. The repo can be found here: https://github.com/CodeDead/deadlock-dotnet-sdk
This should solve the problem of running it in your own environment, and with additional CLI arguments in case you need them. Since it's a library, it can be extended, forked, and improved upon without breaking the UI side of things. The current repository will no longer be .NET oriented, in the future. As for the User-interface side of things, I have decided to migrate the desktop application to Tauri and utilize Rust for the Windows API calls instead of .NET in addition to a React frontend written entirely in JavaScript.
This will produce modern code, with a very tiny binary that does not require .NET at all. This should close this problem. I would recommend discussing everything in regards to the .NET library here: https://github.com/CodeDead/deadlock-dotnet-sdk
Feel free to edit this issue as you see fit, CodeDead.
Goals
Current
DeadLock.Core.Language
localizations--unlock
switch argument to immediately unlock the files/directories specified via startup arguments. Aids Goal 2.Future