[NETSDKE2E][Workload Sets] With manifest mode and workload installed, Unhandled exception occurs when running dotnet workload --info using global.json

[NicoleWang001]

Describe the bug

With manifest mode and workload installed, Unhandled exception occurs when running 'dotnet workload --info using global.json

To Reproduce

1. Install .NET 8.0.400 SDK

2. Install workload eg. aspire
   dotnet workload install aspire
   

3. New a global.json and add workloadverion to this file under a new folder

    c:\tt\TestWithGloabalJson
    cd c:\tt\TestWithGloabalJson
    dotnet new global.json

    {
      "sdk": {
        "version": "8.0.400",
        "workloadVersion": "8.0.400"
      }
    }

4. Run dotnet workload --info and observe

Expected Result

Proper suggestion without any exception. eg. 'dotnet workload list'

Actual Result

Unhandled exception:

[Forgind]

This issue report looks correct to me, but I consider it slightly lower priority because although it shouldn't be an unhandled exception with a call stack, it is still an error scenario, and the error message is correct.

[vdanche]

@Forgind Currently this bug not fix in net8.0.402. right?

[Forgind]

@Forgind Currently this bug not fix in net8.0.402. right?

It was merged into main last week, so it shouldn't be fixed until 9.0

[vdanche]

@Forgind the latest message for NET9 RC2 as below when running dotnet workload --info using globaljson:

dotnet workload --info, error "Unhandled exception: System.IO.FileNotFoundException..." still remains，right？

dotnet --info， "Workload version 9.0.100, which was specified in..." not display in dotnet --info, is it expected?

dotnet workload --version

note:
dotnet workload list

[Forgind]

@Forgind the latest message for NET9 RC2 as below when running dotnet workload --info using globaljson:

dotnet workload --info, error "Unhandled exception: System.IO.FileNotFoundException..." still remains，right？

dotnet --info， "Workload version 9.0.100, which was specified in..." not display in dotnet --info, is it expected?

dotnet workload --version

note: dotnet workload list

I thought it should be in 9.0, but apparently my pr made it in after we branched, so it's in main but not release/9.0.1xx

I'd be in favor of backporting it. @marcpopMSFT, do we still have enough time?

[marcpopMSFT]

On the one hand, it's a very niche scenario. On the other, we want people to try out workloads in 9.0.100 more broadly. @baronfel @dsplaisted it probably makes sense to take this for GA as the fix looks reasonable enough. Thoughts?
https://github.com/dotnet/sdk/pull/42630/files

[dsplaisted]

Here's a PR backporting this to 9.0.1xx: #43587

[Forgind]

9.0.2xx now, it seems

[vdanche]

9.0.2xx now, it seems

On net9 rc2 candidate build --9.0.100-rc.2.24474.11: still display as below after running dotnet workload --info using globaljson

[Forgind]

9.0.2xx now, it seems

On net9 rc2 candidate build --9.0.100-rc.2.24474.11: still display as below after running dotnet workload --info using globaljson

That's still 9.0.1xx. It won't be fixed until 9.0.2xx assuming the current PR goes through.

[vdanche]

@Forgind Fixed on 9.0.200-preview.0.24512.3 sdk, thanks.
dotnet workload --info

dotnet --info:

Currently, still not fix on net9 rtm sdk(9.0.100-rtm.24514.22)

[Forgind]

It won't be fixed on 9.0.100, so there's no need to test that.