this post was submitted on 26 Dec 2023
5 points (77.8% liked)

.NET

1454 readers
21 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] SmartmanApps 1 points 9 months ago

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.