J. Zebedee

I'm having the same issue

Directory junctions are still not working, and will result in operations on valid repositories failing as contents are not detected through junction paths ``` ./restic.exe version restic 0.11.0 compiled with...

Yeah, restic on windows completely ignores junctions. The only workaround I found is to run restic in WSL (which already follows Windows links) or run restic server in WSL/Docker and...

> @jzebedee That error message is completely different from the initial problem in this issue, please open a new issue. > > Where are directory junctions involved? That error message...

> Please, implement this. It's been 2 years It's pretty clear restic is just unsupported/abandonware on Windows. It's had data loss inducing bugs with both backup and restore containing symlinks/junctions...

[Here's the WCT MVVM documentation for migrating from MvvmLight](https://docs.microsoft.com/en-us/windows/communitytoolkit/mvvm/migratingfrommvvmlight). The changes should be in line with this.

Sounds like a good use case for the `aria-` elements.

I can confirm that I have the same issue using the 2.5.15 nuget package.

The `libstt.so` and `libkenlm.so` in the `libstt.tflite.Windows` archive are both Windows DLLs: ``` > wsl file libstt.so libstt.so: PE32+ executable (DLL) (console) x86-64, for MS Windows > wsl file libkenlm.so...

I never ported this, but others have. I'll look into rolling vcdiff into a later version. * [Metric](https://github.com/Metric) completed a [.NET port of open-vcdiff](https://github.com/metric/vcdiff) * [Ronny Chan](https://github.com/chyyran/) [updated and vectorized](https://snowflakepowe.red/blog/adventures-in-c-sharp-optimization-2020-02-15)...