Conversation
4.8 is the last version supported by Windows 7. The code doesn't use any features specific to 4.8.1 so there's no technical reason to use that.
|
GitHub isn't the canonical, so these PR can't be merged. Also, Windows 7 doesn't support TLS 1.3, so is mostly useless for using AWB with a lot of sites... |
I've checked https://sourceforge.net/projects/autowikibrowser/, https://sourceforge.net/p/autowikibrowser/wiki/Home/, https://en.wikipedia.org/wiki/Wikipedia:AutoWikiBrowser, https://en.wikipedia.org/wiki/Wikipedia:AutoWikiBrowser/User_manual -- none has any info on how to contribute. SF UI doesn't have any elements to submit any code, either. |
I can successfully connect to everything in The main idea is, because the code doesn't use any 4.8.1-specific features, there's no technical benefit to use it over 4.8. As per What's new in .NET Framework 4.8.1 | Microsoft Learn, the only potentially relevant difference is an ability to target ARM64 -- but you build for AnyCPU so that doesn't apply. Just to be extra sure, I've double checked if 4.8.1 JITs into native ARM64 code -- and it looks like it doesn't: as per How to run .NET Framework apps natively on Arm64 devices - Visual Studio Blog, that's rather governed by a separate VS project setting that only has an effect in ARM64 Windows 11 24H2 and is independent from the used .NET Framework version (and you aren't using it, either, anyway). |
Somewhere else (not on the above 4 pages), I noticed the mention of Phabricator. I did find AWB there. But there's no way to contribute (or review) code there, either! Should I just attach a patch to the created ticket or something? |
2 participants
4.8 is the last version supported by Windows 7.
The code doesn't use any features specific to 4.8.1 so there's no technical reason to use that.