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*
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
Yeh it’s not great. I’ve got no idea who made the decision to uninstall net6 as part of the update to VS17.4. We were caught by this because it also uninstalls Android 31 SDK which is required for net6-android applications to build. Net6 is an LTS version, so should be installed and be available. I know a lot of projects are pinning to net6. Frustrating to say the least Nick Randolph | Built to Roam Pty Ltd | Co-Founder, Technical Director | +61 412 413 425 | 1300 613 140 | www.builttoroam.com<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.builtt...> The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: Dr Greg Low via ozdotnet <ozdotnet@ozdotnet.com> Sent: Thursday, 10 November 2022 10:42 AM To: ozDotNet <ozdotnet@ozdotnet.com> Cc: Greg Keogh <gfkeogh@gmail.com>; Dr Greg Low <greg@sqldownunder.com> Subject: RE: Visual Studio 17.4.0 side effects 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<mailto:ozdotnet@ozdotnet.com>> Sent: Thursday, 10 November 2022 10:34 AM To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> Cc: Greg Keogh <gfkeogh@gmail.com<mailto: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
@Nick Randolph<mailto:nick@builttoroam.com> Your android bug is getting traction. @Greg Keogh<mailto:gfkeogh@gmail.com> How did the uninstall of the 6.0 SDK break your project? Are you pinning versions via global.json? From: Nick Randolph via ozdotnet <ozdotnet@ozdotnet.com> Sent: Thursday, November 10, 2022 10:46 AM To: ozDotNet <ozdotnet@ozdotnet.com> Cc: Greg Keogh <gfkeogh@gmail.com>; Greg Low <greg@sqldownunder.com>; Nick Randolph <nick@builttoroam.com> Subject: RE: Visual Studio 17.4.0 side effects Yeh it's not great. I've got no idea who made the decision to uninstall net6 as part of the update to VS17.4. We were caught by this because it also uninstalls Android 31 SDK which is required for net6-android applications to build. Net6 is an LTS version, so should be installed and be available. I know a lot of projects are pinning to net6. Frustrating to say the least Nick Randolph | Built to Roam Pty Ltd | Co-Founder, Technical Director | +61 412 413 425 | 1300 613 140 | www.builttoroam.com<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.builtt...> The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: Dr Greg Low via ozdotnet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> Sent: Thursday, 10 November 2022 10:42 AM To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> Cc: Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>>; Dr Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: RE: Visual Studio 17.4.0 side effects 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsqldownunder.com%2F&data=05%7C01%7Cdavid.kean%40microsoft.com%7C4431a12c2d4e42691f6208dac2acf1f3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638036346066013448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=Bx7XvFNdNDPBTt0EjnAIsSuMuAqpdukmv%2B1TOpv%2FnqU%3D&reserved=0> | About Greg: https://about.me/greg.low<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fabout.me%2Fgreg.low&data=05%7C01%7Cdavid.kean%40microsoft.com%7C4431a12c2d4e42691f6208dac2acf1f3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638036346066013448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=5nBMhj8Neb5kYqEc%2BaSEagAhuk9KXro6lu93zbCF2Dk%3D&reserved=0> From: Greg Keogh via ozdotnet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> Sent: Thursday, 10 November 2022 10:34 AM To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> Cc: Greg Keogh <gfkeogh@gmail.com<mailto: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
@Greg Keogh <gfkeogh@gmail.com> How did the uninstall of the 6.0 SDK break your project? Are you pinning versions via global.json?
I just accepted the update and let it run to completion smoothly. A short time later I ran a dotnet command and it said that SDK 6 was needed. I saw in Control Panel that only SDK 7 was installed, so I reinstalled 6 and I was back to normal. Strangely, a colleague did the same thing and didn't see that happen. No pinning anywhere. I'll revisit the pros and cons. *Greg*
The SDK itself is fully backwards compatible. Regardless of whether the runtime itself is LTS, barring workarounds for bugs there should be no need to pin SDKs. * dotnet command and it said that SDK 6 was needed Can you remember what you executed? From: Greg Keogh <gfkeogh@gmail.com> Sent: Friday, November 11, 2022 8:37 AM To: David Kean <David.Kean@microsoft.com> Cc: ozDotNet <ozdotnet@ozdotnet.com>; Nick Randolph <nick@builttoroam.com>; Greg Low <greg@sqldownunder.com> Subject: Re: Visual Studio 17.4.0 side effects @Greg Keogh<mailto:gfkeogh@gmail.com> How did the uninstall of the 6.0 SDK break your project? Are you pinning versions via global.json? I just accepted the update and let it run to completion smoothly. A short time later I ran a dotnet command and it said that SDK 6 was needed. I saw in Control Panel that only SDK 7 was installed, so I reinstalled 6 and I was back to normal. Strangely, a colleague did the same thing and didn't see that happen. No pinning anywhere. I'll revisit the pros and cons. Greg
The SDK itself is fully backwards compatible. Regardless of whether the runtime itself is LTS, barring workarounds for bugs there should be no need to pin SDKs.
I have only pinned once ever, and it was for a known problem in 603(?) which caused VS web service publish to fail and I had to force the publish to use 602. Publishing for many years has produced random bizarre failures, but it looks like 17.4 has fixed that.
- dotnet command and it said that SDK 6 was needed
Can you remember what you executed?
I think it was a web api publish. The output window luckily gave me a clear message (which I didn't record). *Greg*
Lol… you’ve met workloads, right? Over the last 6 months I’ve had to switch sdk pinning on and off with almost regular routine due to various issues with workloads. I find it ironic that Microsoft introduces LTS and then wonders why developers start pinning their projects to the LTS version? Nick Randolph | Built to Roam Pty Ltd | Co-Founder, Technical Director | +61 412 413 425 | 1300 613 140 | www.builttoroam.com<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.builtt...> The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: David Kean <David.Kean@microsoft.com> Sent: Friday, 11 November 2022 9:02 AM To: Greg Keogh <gfkeogh@gmail.com> Cc: ozDotNet <ozdotnet@ozdotnet.com>; Nick Randolph <nick@builttoroam.com>; Greg Low <greg@sqldownunder.com> Subject: RE: Visual Studio 17.4.0 side effects The SDK itself is fully backwards compatible. Regardless of whether the runtime itself is LTS, barring workarounds for bugs there should be no need to pin SDKs. * dotnet command and it said that SDK 6 was needed Can you remember what you executed? From: Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Sent: Friday, November 11, 2022 8:37 AM To: David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: Re: Visual Studio 17.4.0 side effects @Greg Keogh<mailto:gfkeogh@gmail.com> How did the uninstall of the 6.0 SDK break your project? Are you pinning versions via global.json? I just accepted the update and let it run to completion smoothly. A short time later I ran a dotnet command and it said that SDK 6 was needed. I saw in Control Panel that only SDK 7 was installed, so I reinstalled 6 and I was back to normal. Strangely, a colleague did the same thing and didn't see that happen. No pinning anywhere. I'll revisit the pros and cons. Greg
LTS is a runtime concept, not a SDK concept. SDKs are designed to be backwards compatible so the policy for quite a few years has been to install the new version and remove the old version and projects are supposed to continue to build. I have not been involved in the tooling around this for a few years so am out of the loop. My aim with this conversation is to get actionable bugs to bring back to the owning team where projects are failing to build, hence my questions. I am not speaking for the team, I'm just trying to get bugs filed so that we fix these issues. From: Nick Randolph <nick@builttoroam.com> Sent: Friday, November 11, 2022 1:10 PM To: David Kean <David.Kean@microsoft.com>; Greg Keogh <gfkeogh@gmail.com> Cc: ozDotNet <ozdotnet@ozdotnet.com>; Greg Low <greg@sqldownunder.com> Subject: RE: Visual Studio 17.4.0 side effects Lol... you've met workloads, right? Over the last 6 months I've had to switch sdk pinning on and off with almost regular routine due to various issues with workloads. I find it ironic that Microsoft introduces LTS and then wonders why developers start pinning their projects to the LTS version? Nick Randolph | Built to Roam Pty Ltd | Co-Founder, Technical Director | +61 412 413 425 | 1300 613 140 | www.builttoroam.com<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.builtt...> The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>> Sent: Friday, 11 November 2022 9:02 AM To: Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: RE: Visual Studio 17.4.0 side effects The SDK itself is fully backwards compatible. Regardless of whether the runtime itself is LTS, barring workarounds for bugs there should be no need to pin SDKs. * dotnet command and it said that SDK 6 was needed Can you remember what you executed? From: Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Sent: Friday, November 11, 2022 8:37 AM To: David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: Re: Visual Studio 17.4.0 side effects @Greg Keogh<mailto:gfkeogh@gmail.com> How did the uninstall of the 6.0 SDK break your project? Are you pinning versions via global.json? I just accepted the update and let it run to completion smoothly. A short time later I ran a dotnet command and it said that SDK 6 was needed. I saw in Control Panel that only SDK 7 was installed, so I reinstalled 6 and I was back to normal. Strangely, a colleague did the same thing and didn't see that happen. No pinning anywhere. I'll revisit the pros and cons. Greg
Offline I've started a conversation with folks that own the LTS policy, I can understand how this is all very murky - I read the policy and even I'm confused. From: David Kean via ozdotnet <ozdotnet@ozdotnet.com> Sent: Friday, November 11, 2022 4:03 PM To: Nick Randolph <nick@builttoroam.com>; Greg Keogh <gfkeogh@gmail.com> Cc: ozDotNet <ozdotnet@ozdotnet.com>; Greg Low <greg@sqldownunder.com>; David Kean <David.Kean@microsoft.com> Subject: RE: Visual Studio 17.4.0 side effects LTS is a runtime concept, not a SDK concept. SDKs are designed to be backwards compatible so the policy for quite a few years has been to install the new version and remove the old version and projects are supposed to continue to build. I have not been involved in the tooling around this for a few years so am out of the loop. My aim with this conversation is to get actionable bugs to bring back to the owning team where projects are failing to build, hence my questions. I am not speaking for the team, I'm just trying to get bugs filed so that we fix these issues. From: Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>> Sent: Friday, November 11, 2022 1:10 PM To: David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>>; Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: RE: Visual Studio 17.4.0 side effects Lol... you've met workloads, right? Over the last 6 months I've had to switch sdk pinning on and off with almost regular routine due to various issues with workloads. I find it ironic that Microsoft introduces LTS and then wonders why developers start pinning their projects to the LTS version? Nick Randolph | Built to Roam Pty Ltd | Co-Founder, Technical Director | +61 412 413 425 | 1300 613 140 | www.builttoroam.com<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.builtt...> The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>> Sent: Friday, 11 November 2022 9:02 AM To: Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: RE: Visual Studio 17.4.0 side effects The SDK itself is fully backwards compatible. Regardless of whether the runtime itself is LTS, barring workarounds for bugs there should be no need to pin SDKs. * dotnet command and it said that SDK 6 was needed Can you remember what you executed? From: Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Sent: Friday, November 11, 2022 8:37 AM To: David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: Re: Visual Studio 17.4.0 side effects @Greg Keogh<mailto:gfkeogh@gmail.com> How did the uninstall of the 6.0 SDK break your project? Are you pinning versions via global.json? I just accepted the update and let it run to completion smoothly. A short time later I ran a dotnet command and it said that SDK 6 was needed. I saw in Control Panel that only SDK 7 was installed, so I reinstalled 6 and I was back to normal. Strangely, a colleague did the same thing and didn't see that happen. No pinning anywhere. I'll revisit the pros and cons. Greg
FWIW my assumption would be that I can build and run an app that's built with any of the currently supported versions (ie if I pin an app to net6 or net7 I should be able to build and run it with the installed tools but not necessarily a net5 app, since that's out of support). Nick Randolph | Built to Roam Pty Ltd | Co-Founder, Technical Director | +61 412 413 425 | 1300 613 140 | www.builttoroam.com<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.builtt...> The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: David Kean <David.Kean@microsoft.com> Sent: Friday, 11 November 2022 4:15 PM To: ozDotNet <ozdotnet@ozdotnet.com>; Nick Randolph <nick@builttoroam.com>; Greg Keogh <gfkeogh@gmail.com> Cc: Greg Low <greg@sqldownunder.com> Subject: RE: Visual Studio 17.4.0 side effects Offline I've started a conversation with folks that own the LTS policy, I can understand how this is all very murky - I read the policy and even I'm confused. From: David Kean via ozdotnet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> Sent: Friday, November 11, 2022 4:03 PM To: Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>>; Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>>; David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>> Subject: RE: Visual Studio 17.4.0 side effects LTS is a runtime concept, not a SDK concept. SDKs are designed to be backwards compatible so the policy for quite a few years has been to install the new version and remove the old version and projects are supposed to continue to build. I have not been involved in the tooling around this for a few years so am out of the loop. My aim with this conversation is to get actionable bugs to bring back to the owning team where projects are failing to build, hence my questions. I am not speaking for the team, I'm just trying to get bugs filed so that we fix these issues. From: Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>> Sent: Friday, November 11, 2022 1:10 PM To: David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>>; Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: RE: Visual Studio 17.4.0 side effects Lol... you've met workloads, right? Over the last 6 months I've had to switch sdk pinning on and off with almost regular routine due to various issues with workloads. I find it ironic that Microsoft introduces LTS and then wonders why developers start pinning their projects to the LTS version? Nick Randolph | Built to Roam Pty Ltd | Co-Founder, Technical Director | +61 412 413 425 | 1300 613 140 | www.builttoroam.com<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.builtt...> The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>> Sent: Friday, 11 November 2022 9:02 AM To: Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: RE: Visual Studio 17.4.0 side effects The SDK itself is fully backwards compatible. Regardless of whether the runtime itself is LTS, barring workarounds for bugs there should be no need to pin SDKs. * dotnet command and it said that SDK 6 was needed Can you remember what you executed? From: Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Sent: Friday, November 11, 2022 8:37 AM To: David Kean <David.Kean@microsoft.com<mailto:David.Kean@microsoft.com>> Cc: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>; Nick Randolph <nick@builttoroam.com<mailto:nick@builttoroam.com>>; Greg Low <greg@sqldownunder.com<mailto:greg@sqldownunder.com>> Subject: Re: Visual Studio 17.4.0 side effects @Greg Keogh<mailto:gfkeogh@gmail.com> How did the uninstall of the 6.0 SDK break your project? Are you pinning versions via global.json? I just accepted the update and let it run to completion smoothly. A short time later I ran a dotnet command and it said that SDK 6 was needed. I saw in Control Panel that only SDK 7 was installed, so I reinstalled 6 and I was back to normal. Strangely, a colleague did the same thing and didn't see that happen. No pinning anywhere. I'll revisit the pros and cons. Greg
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.
Yes indeed, you mentioned that a few months ago, and it happened to me a few days ago. I opened a project archived about last Xmas to compare some code with its replacement and I received shedloads of errors trying to compile and run it, I could have spent a solid hour resurrecting it with tfm or package updates, but I gave up and just browsed the raw files. Sometimes projects I compiled last Friday won't work this week. The person who should be taken to the Hague and prosecuted for crimes against software is Mr Newtonsoft. I wonder if other people here have burned major parts of their lives away trying to solve Newtonsoft conflicts and crashes. He's not totally to blame though, because major players have become dependent on it, which combined with its dodgy versioning system has created a tangle worse than string theory. I'm glad to see Microsoft is gradually removing it from their libraries, the worst being Cosmos DB which keeps dragging it in (but I think it's gone in the latest libraries I'm not using yet). End of rant. P.S. I just found that one of my vanilla hobby Blazor apps is also stalling like the big apps. Now I suspect there is some new global compatibility or config mismatch issue. The only players are VS2022 and Chrome, so what they hell has happened to their friendship?! *GK*
Blazor fix Update these two packages to 6.0.11, the last of the v6 series. Include="Microsoft.AspNetCore.Components.WebAssembly" Version="6.0.11" /> Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version=" 6.0.11" You are offered 7.0.0 as the latest, but they will not install in a net60 project. One old project had 6.0.3 and another 6.0.10 which both stalled. *GK*
participants (4)
-
David Kean -
Dr Greg Low -
Greg Keogh -
Nick Randolph