will take a shoot at the branch in ~30-60min

from the issue:

IIRC I might have seen a reference to System.Reactive (dotnet/réactive)
(i did not fully check that this affirmation is actually true)

given the changes in recent prview about breaking changes regarding WinRT
Also Rx have dependencies towards WinRt (scheduler maybe ?)

You might want to recheck that the code of this repo using Rx still runs on RC1

especially after this comment from yesterday:

dotnet/reactive#1237 (comment)

I do confirm that fixes the bug from VS here too

did not checked the Rx part in Hosting

E2E seems also affected by project.assets.json somehow :D

the generated csproj is

<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
    <RootNamespace>Frontend</RootNamespace>
  </PropertyGroup>

  <ItemGroup>
    <ProjectReference Include="$(TyeLibrariesPath)\Microsoft.Tye.Extensions.Configuration\Microsoft.Tye.Extensions.Configuration.csproj" />
  </ItemGroup>

</Project>

Copy pasting all the test project aside, works once i move this project somwhere else on disk and run dotnet build manually with a global.json pointing to RC1

more info :

@JunTaoLuo
I'm observing a strange behavior in dotnet restore and dotnet build on the generated proj file
I'm not really sure but it look like there's no "SDK" imported so when Build target is ran, it does not know about restore
Also running only restore does nothing

The result is that project.assets.json are missing

thx @JunTaoLuo for #674, rebasing this one seems ok now
This fixes the previous failure during E2E, especially the dotnet restore that now ... restore :D

I can't explain how most of the test used docker but not these :D

Huh yea maybe those tests need to have updated conditions. I have Docker installed an running on my machines so I never noticed. FYI, I'm going to close this PR in favour of #668. That PR is our automation catching up with the SDK versions.

docker detection seems flacky, I even added a throw in that ConditionalFact ... never throw even on rebuild, or clear all
had to re-run ./restore I think eventually all ran
I think the same happened month ago in dotnet/aspnetcore regarding SignalR and redis tests