One of my dreams is to be able to open a VS project that I haven’t touched for 6 months, and have it still just work. Far too frequently, I spend an eternity in dependency hell. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile SQL Down Under | Web: https://sqldownunder.com<https://sqldownunder.com/> | About Greg: https://about.me/greg.low From: Greg Keogh via ozdotnet <ozdotnet@ozdotnet.com> Sent: Thursday, 10 November 2022 10:34 AM To: ozDotNet <ozdotnet@ozdotnet.com> Cc: Greg Keogh <gfkeogh@gmail.com> Subject: Visual Studio 17.4.0 side effects Folks, I accepted the major update yesterday, and this morning some odd things are happening. I noticed that .NET SDK 6 was gone and 7 was installed. I had to manually reinstall SDK 6 to get going again (this didn't happen to a colleague). A WebApi project produced a huge slab of NU1106 compile errors. I removed every reference of every type and it made no difference. After 2 hours I discovered that if I removed one of my own rather innocuous project references then it all came good. That reference has been there for the last 6 months. Now all of my existing Blazor projects stall and produce something like this: Failed to launch debug adapter. Additional information may be available in the output window. Unable to launch browser: "Could not open ws://localhost:56709/_framework/debug/ws-proxy?browser=wsAFF127.0.0.1A59317FdevtoolsFbrowserF4fe90d5b-f3d4-4f84-950c-2cc9af15b95c" The program '' has exited with code 4294967295 (0xffffffff). I've now spent 2 hours on this, and it's not looking helpful. A brand new app runs okay. I've run out of ideas. I started work at 06:30 but I haven't done any real work yet. Greg Keogh