Closed jwilo closed 3 months ago
I have just updated Visual Studio 17.10.5, in which the problem appears to be resolved
Microsoft Visual Studio Community 2022
Version 17.10.5
VisualStudio.17.Release/17.10.5+35122.118
Microsoft .NET Framework
Version 4.8.09037
Environment
.NET version
.NET 8.0.3
Did this work in a previous version of Visual Studio and/or previous .NET release?
Same .NET version, but a slightly older version of VS, unfortunately I do not know which version, though I updated around March, and again only a few weeks ago when the problem arose
Issue description
An exact reoccurence of closed issue #11473 raised by @gen-angry
Steps to reproduce
As per #11473
Diagnostics
No response