4
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Dec 2023
4 points (75.0% liked)
.NET
1869 readers
1 users here now
Getting started
Useful resources
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
- Rule 4: Submit the original source. If a post reports on something found on another site, submit the latter
Related communities
Wikipedia pages
- .NET (open source & cross platform)
- .NET Framework (proprietary & Windows-only)
founded 3 years ago
MODERATORS
Just an update on this. There's been an update to the issue on the 10th of January with "Under Investigation. This issue is currently being investigated...", which is a nice change from "more info needed", or even worse "this isn't a bug it's a feature", so they've managed to reproduce the bug and are looking into it.
This means if you see the 17.8.4 update available message, the fix isn't in there, so don't update yet. I'm using 17.8.0 - I'm not sure if the bug was introduced in 17.8.1, 17.8.2, or 17.8.3, but 17.8.0 is definitely safe to use.