RE: Visual Studio 17.4.0 side effects

[Nick Randolph]

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.builttoroam.com%2F=04%7C01%7Caleader%40microsoft.com%7Ce982eb8653db4ed808cd08d8bb5c83fd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637465353324748425%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=5zqg1UrX2OMBH0rP%2BSrOQYlPe6d2Vcbm91%2Fnup6kZuQ%3D=0>
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 
Sent: Friday, 11 November 2022 4:15 PM
To: ozDotNet ; Nick Randolph ; 
Greg Keogh 
Cc: Greg Low 
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 
mailto:ozdotnet@ozdotnet.com>>
Sent: Friday, November 11, 2022 4:03 PM
To: Nick Randolph mailto:n...@builttoroam.com>>; Greg 
Keogh mailto:gfke...@gmail.com>>
Cc: ozDotNet mailto:ozdotnet@ozdotnet.com>>; Greg Low 
mailto:g...@sqldownunder.com>>; David Kean 
mailto:david.k...@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 mailto:n...@builttoroam.com>>
Sent: Friday, November 11, 2022 1:10 PM
To: David Kean mailto:david.k...@microsoft.com>>; 
Greg Keogh mailto:gfke...@gmail.com>>
Cc: ozDotNet mailto:ozdotnet@ozdotnet.com>>; Greg Low 
mailto:g...@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.builttoroam.com%2F=05%7C01%7Cdavid.kean%40microsoft.com%7Cac8c57ce02a74c01eb7a08dac3a2501b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638037400076295789%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=MtwqOXEh3TKTch%2FOrDys2FM74HGgs7rrk6c48MOaJCM%3D=0>
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 mailto:david.k...@microsoft.com>>
Sent: Friday, 11 November 2022 9:02 AM
To: Greg Keogh mailto:gfke...@gmail.com>>
Cc: ozDotNet mailto:ozdotnet@ozdotnet.com>>; Nick 
Randolph mailto:n...@builttoroam.com>>; Greg Low 
mailto:g...@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 mailto:gfke...@gmail.com>>
Sent: Friday, November 11, 2022 8:37 AM
To: David Kean mailto:david.k...@microsoft.com>>
Cc: ozDotNet mailto:ozdotnet@ozdotnet.com>>; Nick 
Randolph mailto:n...@builttoroam.com>>; Greg Low 
mailto:g...@sqldownunder.com>>
Subject: Re: Visual Studio 17.4.0 side effects

@Greg Keogh<mailto:gfke.

RE: Visual Studio 17.4.0 side effects

[David Kean]

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 
Sent: Friday, November 11, 2022 4:03 PM
To: Nick Randolph ; Greg Keogh 
Cc: ozDotNet ; Greg Low ; David 
Kean 
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 mailto:n...@builttoroam.com>>
Sent: Friday, November 11, 2022 1:10 PM
To: David Kean mailto:david.k...@microsoft.com>>; 
Greg Keogh mailto:gfke...@gmail.com>>
Cc: ozDotNet mailto:ozdotnet@ozdotnet.com>>; Greg Low 
mailto:g...@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.builttoroam.com%2F=05%7C01%7Cdavid.kean%40microsoft.com%7Cac8c57ce02a74c01eb7a08dac3a2501b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638037400076295789%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=MtwqOXEh3TKTch%2FOrDys2FM74HGgs7rrk6c48MOaJCM%3D=0>
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 mailto:david.k...@microsoft.com>>
Sent: Friday, 11 November 2022 9:02 AM
To: Greg Keogh mailto:gfke...@gmail.com>>
Cc: ozDotNet mailto:ozdotnet@ozdotnet.com>>; Nick 
Randolph mailto:n...@builttoroam.com>>; Greg Low 
mailto:g...@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 mailto:gfke...@gmail.com>>
Sent: Friday, November 11, 2022 8:37 AM
To: David Kean mailto:david.k...@microsoft.com>>
Cc: ozDotNet mailto:ozdotnet@ozdotnet.com>>; Nick 
Randolph mailto:n...@builttoroam.com>>; Greg Low 
mailto:g...@sqldownunder.com>>
Subject: Re: Visual Studio 17.4.0 side effects

@Greg Keogh<mailto:gfke...@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

RE: Visual Studio 17.4.0 side effects

[David Kean]

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 
Sent: Friday, November 11, 2022 1:10 PM
To: David Kean ; Greg Keogh 
Cc: ozDotNet ; Greg Low 
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.builttoroam.com%2F=05%7C01%7CDavid.Kean%40microsoft.com%7Ccbf1ef1f49e94b3e0a6f08dac389cc73%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638037293893670660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=Z%2ByYajdUNtHHWp%2FnjKPA%2FHIfTlKZLCp3uYvGEqOKKFI%3D=0>
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 mailto:david.k...@microsoft.com>>
Sent: Friday, 11 November 2022 9:02 AM
To: Greg Keogh mailto:gfke...@gmail.com>>
Cc: ozDotNet mailto:ozdotnet@ozdotnet.com>>; Nick 
Randolph mailto:n...@builttoroam.com>>; Greg Low 
mailto:g...@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 mailto:gfke...@gmail.com>>
Sent: Friday, November 11, 2022 8:37 AM
To: David Kean mailto:david.k...@microsoft.com>>
Cc: ozDotNet mailto:ozdotnet@ozdotnet.com>>; Nick 
Randolph mailto:n...@builttoroam.com>>; Greg Low 
mailto:g...@sqldownunder.com>>
Subject: Re: Visual Studio 17.4.0 side effects

@Greg Keogh<mailto:gfke...@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

Re: Visual Studio 17.4.0 side effects

[Greg Keogh]

>
> 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*

RE: Visual Studio 17.4.0 side effects

[David Kean]

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 
Sent: Friday, November 11, 2022 8:37 AM
To: David Kean 
Cc: ozDotNet ; Nick Randolph ; 
Greg Low 
Subject: Re: Visual Studio 17.4.0 side effects

@Greg Keogh<mailto:gfke...@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

Re: Visual Studio 17.4.0 side effects

[Greg Keogh]

>
> @Greg Keogh  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*

RE: Visual Studio 17.4.0 side effects

[David Kean]

@Nick Randolph<mailto:n...@builttoroam.com> Your android bug is getting 
traction.

@Greg Keogh<mailto:gfke...@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 
Sent: Thursday, November 10, 2022 10:46 AM
To: ozDotNet 
Cc: Greg Keogh ; Greg Low ; Nick 
Randolph 
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.builttoroam.com%2F=05%7C01%7Cdavid.kean%40microsoft.com%7C4431a12c2d4e42691f6208dac2acf1f3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638036346066013448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=6CEmENe9kbl2FzGihbk5nvotwXeCa3VCX7N2WEwQkkI%3D=0>
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 
mailto:ozdotnet@ozdotnet.com>>
Sent: Thursday, 10 November 2022 10:42 AM
To: ozDotNet mailto:ozdotnet@ozdotnet.com>>
Cc: Greg Keogh mailto:gfke...@gmail.com>>; Dr Greg Low 
mailto:g...@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=05%7C01%7Cdavid.kean%40microsoft.com%7C4431a12c2d4e42691f6208dac2acf1f3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638036346066013448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=Bx7XvFNdNDPBTt0EjnAIsSuMuAqpdukmv%2B1TOpv%2FnqU%3D=0>
 | About Greg:  
https://about.me/greg.low<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fabout.me%2Fgreg.low=05%7C01%7Cdavid.kean%40microsoft.com%7C4431a12c2d4e42691f6208dac2acf1f3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638036346066013448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=5nBMhj8Neb5kYqEc%2BaSEagAhuk9KXro6lu93zbCF2Dk%3D=0>

From: Greg Keogh via ozdotnet 
mailto:ozdotnet@ozdotnet.com>>
Sent: Thursday, 10 November 2022 10:34 AM
To: ozDotNet mailto:ozdotnet@ozdotnet.com>>
Cc: Greg Keogh mailto:gfke...@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 (0x).

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

Re: Visual Studio 17.4.0 side effects

[Greg Keogh]

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*

>

Re: Visual Studio 17.4.0 side effects

[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.
>

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*

RE: Visual Studio 17.4.0 side effects

[Nick Randolph]

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.builttoroam.com%2F=04%7C01%7Caleader%40microsoft.com%7Ce982eb8653db4ed808cd08d8bb5c83fd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637465353324748425%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=5zqg1UrX2OMBH0rP%2BSrOQYlPe6d2Vcbm91%2Fnup6kZuQ%3D=0>
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 
Sent: Thursday, 10 November 2022 10:42 AM
To: ozDotNet 
Cc: Greg Keogh ; Dr Greg Low 
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 
mailto:ozdotnet@ozdotnet.com>>
Sent: Thursday, 10 November 2022 10:34 AM
To: ozDotNet mailto:ozdotnet@ozdotnet.com>>
Cc: Greg Keogh mailto:gfke...@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 (0x).

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

RE: Visual Studio 17.4.0 side effects

[Dr Greg Low]

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 | 
About Greg:  https://about.me/greg.low

From: Greg Keogh via ozdotnet 
Sent: Thursday, 10 November 2022 10:34 AM
To: ozDotNet 
Cc: Greg Keogh 
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 (0x).

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