Antony Male

I _think_ there are 3 separate issues here? 1. But when there are lots of files, the text isn't readable completely (see screenshot). 2. "files" and "directories" aren't yet translated....

> We should (maybe) have each language name in that language instead of English. So instead of > English, German, French, ... > we would have > English, Deutsch, Français,...

> But when there are lots of files, the text isn't readable completely (see screenshot). There's a new issue, #3710, which tracks this.

Just to add: there's no harm in targeting an old version of .NET for a library. The library will run on whatever runtime the user compiles their application for. Targeting...

> keeping the .NETStandard2.0 target may create a false sense of support for these runtimes. That's not normally a concern. Targetting .NET Standard 2.0 just means that you only need...

Alternatively, have a big "Troubleshoot connection issues" button, and just do the connection test when clicked. That should reduce the load a lot. It also means you could hive the...

I'll take a look next time I get the chance, thanks!

Yes, I can still replicate this in 1.11. It doesn't look like any of the files in the stack trace have been changed in any meaningful way? Is there a...

Yes, I can still replicate this on 1.11. This perhaps isn't surprising, as it doesn't look like any of the files in the stack trace have been modified in any...

FWIW, this is what I did on foxess_modbus: https://github.com/nathanmarlor/foxess_modbus/compare/91cdc65...322fca77847dac4804f65302ea19b3a303865fb2. When I create a tag, it creates a zip of the integration (with an updated `manifest.json` containing the version number from...