Roadplan about deadlock HOT 2 CLOSED

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

from deadlock.

Motivation

I'm planning to have HaloSPV3/HXE reference or invoke DeadLock as a library or CLI tool to unlock files in the background.

• HXE is a wrapper for haloce.exe. Before invoking haloce.exe, HXE will apply patches to fix bugs or toggle features. Users of HXE have found that its patcher will fail when haloce.exe is locked by another process.
• One of HXE's W.I.P. features is a wrapper for Windows' DeviceIoControl function with the FSCTL_SET_COMPRESSION control code. As the two names suggest, this wrapper adds the DirectoryInfo.Compress() and FileInfo.Compress() extensions for applying LZNT1 compression on NTFS file systems. The most frequently encountered Win32ErrorCode during tests is ERROR_SHARING_VIOLATION (32): "The process cannot access the file because it is being used by another process".

from deadlock.