Update sdk to 7.0.100-alpha.1.21470.6

[halter73]

No description provided.

[dougbu]

@wtgodbe is this SDK new enough to undo any of the workarounds added in #36328❔ If yes, I suggest adding comments to remind us what we'll likely need to change the next time we change TFMs before supporting SDK exists. Also good fodder for your major / minor change doc.

[wtgodbe]

Please update these 2 projects to use DefaultNetCoreTargetFramework

aspnetcore/eng/helix/content/RunTests/RunTests.csproj

Line 5 in 302cfd9

<TargetFramework>net6.0</TargetFramework>

aspnetcore/eng/tools/RepoTasks/RepoTasks.csproj

Line 4 in 302cfd9

<TargetFrameworks>net6.0</TargetFrameworks>

[wtgodbe]

We can update RepoTasks & RunTests now as well

[halter73]

@wtgodbe Updated (4e3bd0e). Should the following also be updated to reference net7.0?

aspnetcore/eng/tools/GenerateFiles/Directory.Build.targets.in

Lines 11 to 27 in 7b09459

	<ItemGroup>
	<KnownAppHostPack
	Include="@(KnownAppHostPack->WithMetadataValue('TargetFramework', 'net6.0'))"
	TargetFramework="${DefaultNetCoreTargetFramework}"
	Condition="@(KnownAppHostPack->Count()) != '0' AND
	!(@(KnownAppHostPack->AnyHaveMetadataValue('TargetFramework', '${DefaultNetCoreTargetFramework}')))" />
	<KnownRuntimePack
	Include="@(KnownRuntimePack->WithMetadataValue('TargetFramework', 'net6.0'))"
	TargetFramework="${DefaultNetCoreTargetFramework}"
	Condition="@(KnownRuntimePack->Count()) != '0' AND
	!(@(KnownRuntimePack->AnyHaveMetadataValue('TargetFramework', '${DefaultNetCoreTargetFramework}')))" />
	<KnownFrameworkReference
	Include="@(KnownFrameworkReference->WithMetadataValue('TargetFramework', 'net6.0'))"
	TargetFramework="${DefaultNetCoreTargetFramework}"
	Condition="@(KnownFrameworkReference->Count()) != '0' AND
	!(@(KnownFrameworkReference->AnyHaveMetadataValue('TargetFramework', '${DefaultNetCoreTargetFramework}')))" />
	</ItemGroup>

It also looks like https://github.com/dotnet/spa-templates needs TFM updates.

[wtgodbe]

Should the following also be updated to reference net7.0?

No, that's copying the previous tfm's frameworkReference but with the current TFM, in case there isn't already a FrameworkReference for the current TFM (which there wasn't before this PR). Spa-Templates should be a simple find/replace, I can take care of it if you want

[wtgodbe]

dotnet/spa-templates#21

[dougbu]

@halter73 @wtgodbe should we run the pipeline again i.e. should the spa-templates submodule update be enough to get this working❔

[dougbu]

/azp run

[dougbu]

🤞

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[dougbu]

@marcpopMSFT @dsplaisted @wli I'm only seeing @(KnownFrameworkReference) items with %(TargetFramework) metadata for netcoreapp3.0, netcoreapp3.1, net5.0, and net6.0. Why isn't net7.0 in there yet❔

(Side note: Why is the SDK still carting around netcoreapp3.0❔)

[dougbu]

@wtgodbe please approve to remove your block on this PR. Can't update RepoTasks yet.

[dougbu]

Must stay at net6.0 in both RepoTasks and RunTests for now. The SDK's understanding of net7.0 isn't complete enough yet.

[dsplaisted]

I'm only seeing @(KnownFrameworkReference) items with %(TargetFramework) metadata for netcoreapp3.0, netcoreapp3.1, net5.0, and net6.0. Why isn't net7.0 in there yet❔

net7.0 targeting support is (hopefully) coming in dotnet/installer#11750.

(Side note: Why is the SDK still carting around netcoreapp3.0❔)

We want people to use the latest SDK, so it will still support building projects targeting .NET Core 1.0 (which didn't use KnownFrameworkReference items, which is why you don't see them prior to version 3). There's not much payload in the .NET SDK for these older versions, pretty much just version numbers which are listed in the BundledVersions props file.

[ghost]

Hi @dsplaisted. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.