[WebToolsE2E]Create web Individual project failed with error “error NU1102: Unable to find package Microsoft.CodeAnalysis.CSharp... with version ... ” after installing SDK 10.0 RC2

[jinzhao1127]

REGRESSION INFO: Works well Previous 10.0 RC 2

Platform

• Windows
• macOS
• Linux

INSTALL STEPS

1. Win11 x64 24h2 ENU
2. Install the latest SDK 10.0 RC2 from: https://aka.ms/dotnet/10.0.1xx/daily/dotnet-sdk-win-x64.exe
3. Apply feed

REPRO STEPS

1.Open a normal command prompt ，create mvc Individual project

md mvc
cd mvc
dotnet new mvc -au Individual

Note:
1.This issue does not reproduce on MVC NoAuth project
2. This issue also reproduce on razor/Blazor web Individual app
3. This issue also reproduce when creating individual app in VS

ACTUAL
Create project failed with error “error NU1102:
Unable to find package Microsoft.CodeAnalysis.CSharp.Workspaces with version (>= 5.0.0-2.25453.107) ”

Error Log:

Restoring C:\Users\v-zhajin\MVC1\MVC1.csproj:
C:\Users\v-zhajin\MVC1\MVC1.csproj : error NU1102:
  Unable to find package Microsoft.CodeAnalysis.CSharp.Workspaces with version (>= 5.0.0-2.25453.107)
    - Found 167 version(s) in nuget.org [ Nearest version: 4.14.0 ]
    - Found 87 version(s) in net10 [ Nearest version: 5.0.0-1.25259.101 ]
C:\Users\v-zhajin\MVC1\MVC1.csproj : error NU1102:
  Unable to find package Microsoft.CodeAnalysis.Workspaces.MSBuild with version (>= 5.0.0-2.25453.107)
    - Found 112 version(s) in nuget.org [ Nearest version: 4.14.0 ]
    - Found 87 version(s) in net10 [ Nearest version: 5.0.0-1.25259.101 ]
C:\Users\v-zhajin\MVC1\MVC1.csproj : error NU1102:
  Unable to find package Microsoft.Build.Framework with version (>= 17.15.0-preview-25453-107)
    - Found 83 version(s) in net10 [ Nearest version: 17.15.0-preview-25259-101 ]
    - Found 69 version(s) in nuget.org [ Nearest version: 17.15.0-preview-25277-114 ]
C:\Users\v-zhajin\MVC1\MVC1.csproj : error NU1102:
  Unable to find package Microsoft.CodeAnalysis.CSharp with version (>= 5.0.0-2.25453.107)
    - Found 167 version(s) in nuget.org [ Nearest version: 4.14.0 ]
    - Found 87 version(s) in net10 [ Nearest version: 5.0.0-1.25259.101 ]
Restore failed.
Post action failed.
Manual instructions: Run 'dotnet restore'

Dotnet --info

C:\Users\v-zhajin>dotnet --info
.NET SDK:
 Version:           10.0.100-rc.2.25458.103
 Commit:            f7f9fbc789
 Workload version:  10.0.100-manifests.7fbb8a4b
 MSBuild version:   17.15.0-preview-25458-103+f7f9fbc78

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22631
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\10.0.100-rc.2.25458.103\

.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.

Host:
  Version:      10.0.0-rc.2.25458.103
  Architecture: x64
  Commit:       f7f9fbc789

.NET SDKs installed:
  10.0.100-rc.2.25458.103 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 10.0.0-rc.2.25458.103 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 10.0.0-rc.2.25458.103 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 10.0.0-rc.2.25458.103 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

EXPECTED
Create project successfully.

[jinzhao1127]

This is a blocking issue for 10.0 RC 2
cc: @balachir

[vdanche]

Works well on console app

[balachir]

@phil-allen-msft @AbhitejJohn is this your area?

cc: @wtgodbe

[jaredpar]

@dibarbet this seems possibly related to VMR package publishing

[dibarbet]

I haven't merged any changes for VMR publishing yet. It looks like the net10 feed is simply missing preview2 packages.

[mmitche]

I think the validation steps here are wrong. Out of the VMR builds, the tooling packages get published to dotnet-tools. That feed will need to be added for validating rolling daily builds of RC2

[dibarbet]

Issue was introduced for rc2 here - dotnet/efcore#36707

Also related to dotnet/dotnet#2270 (review) but we're in a bit of a pickle here. EFCore is depending on latest Roslyn packages that will not necessarily be published when the SDK releases (we publish on our own cadence due to dependencies on VS packages).