Clean up STJ references Fixes #39902 #40645

Forgind · 2024-05-02T20:26:44Z

First commit removes references to S.T.J that shouldn't be necessary because we have our own "WorkloadManifestReader.SystemTextJson" class.

The second commit forces all our package versions to 8.0.0.

I was a bit confused with this logic:
<UseSystemTextJson Condition="'$(TargetFramework)'!='netstandard2.0' And '$(TargetFramework)'!='net472'">True</UseSystemTextJson>

This seems to say that we should use System.Text.Json on core only

kasperk81 · 2024-05-03T16:56:06Z

src/Resolvers/Microsoft.DotNet.MSBuildSdkResolver/Microsoft.DotNet.MSBuildSdkResolver.csproj


  <ItemGroup Condition="'$(TargetFrameworkIdentifier)' == '.NETFramework'">
-    <PackageReference Include="System.Text.Json"  VersionOverride="8.0.0" />
+    <PackageReference Include="System.Text.Json"  VersionOverride="$(SystemTextJsonPackageVersion)" Condition="'$(TargetFramework)' == 'net472'"/>


duplicate condition (previous line covered it)

I'm just confused why things aren't working the way I'd expect, so I was adding some duplication in case I had missed something, and it didn't work as I'd thought.

marcpopMSFT · 2024-05-08T19:09:04Z

eng/Versions.props

    <SystemSecurityPermissionsPackageVersion>8.0.0</SystemSecurityPermissionsPackageVersion>
    <SystemServiceProcessServiceControllerVersion>8.0.0</SystemServiceProcessServiceControllerVersion>
-    <SystemTextJsonPackageVersion>8.0.2</SystemTextJsonPackageVersion>
+    <SystemTextJsonPackageVersion>8.0.0</SystemTextJsonPackageVersion>


This property is used in directory.packages.props so what you're doing here is actually overriding the version used by transitive pinning (so overriding the version for all implicit .net core references). You'll need a separate property to use for pinning to 8.0.0 and let the d.p.props version float to current. Runtime does this too if you see here: https://github.com/dotnet/runtime/blob/main/eng/Versions.props#L137

FYI, I talked to Eric and I'll be prepping a change for 8.0.1xx and 8.0.3xx for how we handle STJ. We'll want that change in 8.0.4xx as well. It depends on a change in runtime so you won't be able to get this PR working in 4xx as it turns out. You should be able to retarget to main, make the above change, apply my changes, and get it sorted out. I'll talk to you offline as it's complicated as there are actually 3 different classes of STJ references, not 2 like I thought.

Following up on this, I believe there are three categories of project that we talked about:

The four task projects should have STJ references with no version override. Razor and static web assets should have a net472 check but build and publish should not. I recommend looking at the 8.0.3xx internal AzDo branches to confirm:
https://dev.azure.com/dnceng/internal/_git/dotnet-sdk?path=/src/WebSdk/Publish/Tasks/Microsoft.NET.Sdk.Publish.Tasks.csproj&version=GBinternal/release/8.0.3xx&_a=contents

The components we have that build for framework and run in VS should have a reference to STJ for netfx targeting and should have a VersionOverride to version 8.0.0. That's because in these cases, VS is providing STJ and we need to work with whichever version they ship.

No other .net core building projects should have a reference to STJ.

CC @ericstj to confirm. We discussed this in a 1:1 a few weeks ago but didn't write it down so writing it down here now.

This sounds correct. Minimize the places where you ship a copy if you can reference the version provided by your host process.

marcpopMSFT · 2024-07-01T20:02:24Z

src/BuiltInTools/dotnet-watch/dotnet-watch.csproj

-      Explicit System.Text.Json package reference is required for source-build to pick up the live package.
-      Avoids picking up an old version via transitive dependency from Microsoft.Build or Microsoft.CodeAnalysis.Workspaces.MSBuild.
-    -->
-    <PackageReference Include="System.Text.Json" />


Probably want a review from @tmat but with CPM now enabled, this may not be required anymore like it was before.

Having an explicit package reference is no longer required, or removing it is no longer required?

Having the explicit reference is no longer required, I think. If I understand the original issue per the comment, a transitive version was picked up that didn't work with source build and adding the explicit reference up-versioned to one that was supported. CPM should do the version change as well.

marcpopMSFT · 2024-07-01T20:03:56Z

src/Tests/ArgumentsReflector/ArgumentsReflector.csproj

    <Using Remove="Microsoft.NET.TestFramework.Utilities" />
    <Using Remove="Xunit" />
    <Using Remove="Xunit.Abstractions" />
+    <PackageReference Include="System.Text.Json" VersionOverride="$(SystemTextJsonPackageVersion)" />


this is a test so not sure it'll need the version override

marcpopMSFT · 2024-07-01T20:07:50Z

...ers/Microsoft.NET.Sdk.WorkloadManifestReader/Microsoft.NET.Sdk.WorkloadManifestReader.csproj


  <ItemGroup>
-    <PackageReference Include="System.Text.Json" Condition="'$(UseSystemTextJson)'=='True'" />
+    <PackageReference Include="System.Text.Json"


This one will require more investigation. The conditional above that sets UseSystemTextJson is configured for core only which we don't need a reference for so I think we might be able to just remove it from here but you'd have to confirm the framework build doesn't use STJ (as I know things changed so this property may not be accurately named anymore)

marcpopMSFT · 2024-07-01T20:09:50Z

src/Cli/Microsoft.DotNet.Cli.Utils/Microsoft.DotNet.Cli.Utils.csproj

    <PackageReference Include="Microsoft.Build" ExcludeAssets="runtime" PrivateAssets="all" />
    <PackageReference Include="Microsoft.Build.Utilities.Core" ExcludeAssets="runtime" PrivateAssets="all" />
    <PackageReference Include="System.CommandLine" />
+    <PackageReference Include="System.Text.Json" VersionOverride="$(SystemTextJsonPackageVersion)" Condition="'$(TargetFramework)' == 'net472'"/>


where is SystemTextJsonPackageVersion set and what is it set to? I think it should be 8.0.0 but don't see it in this PR (also the name is really close to what darc will update so it may need a slight update to ensure darc doesn't get confused).

I'm starting to think the PR to create the specific package versions was never ported to main. I'll need to investigate.

My PR is now in which should enable you to update the minimum version name #41890

src/Tests/ArgumentsReflector/ArgumentsReflector.csproj

src/Cli/Microsoft.DotNet.Cli.Utils/Microsoft.DotNet.Cli.Utils.csproj

ViktorHofer · 2024-07-22T11:39:50Z

Consider using Toolset instead of Base: https://github.com/dotnet/runtime/blob/7c3286fd62a617a26439d751e3c2ce80fd6599f5/eng/Versions.props#L135-L139

eng/Versions.props

VS has upgraded to STJ 8.0.4, so we can, too

Forgind · 2024-07-29T22:56:59Z

The ubuntu failure appears to be dotnet/source-build#4503

ghost added Area-Infrastructure untriaged Request triage from a team member labels May 2, 2024

Forgind changed the title ~~Clean up STJ references~~ Clean up STJ references Fixes #39902 May 2, 2024

kasperk81 reviewed May 3, 2024

View reviewed changes

marcpopMSFT reviewed May 8, 2024

View reviewed changes

build-analysis bot mentioned this pull request Jun 28, 2024

Failure on Helix tests - Tests timing out #40074

Open

marcpopMSFT reviewed Jul 1, 2024

View reviewed changes

Forgind marked this pull request as ready for review July 11, 2024 21:45

Forgind requested review from a team and vijayrkn as code owners July 11, 2024 21:45

marcpopMSFT reviewed Jul 11, 2024

View reviewed changes

src/Tests/ArgumentsReflector/ArgumentsReflector.csproj Outdated Show resolved Hide resolved

marcpopMSFT reviewed Jul 11, 2024

View reviewed changes

src/Cli/Microsoft.DotNet.Cli.Utils/Microsoft.DotNet.Cli.Utils.csproj Outdated Show resolved Hide resolved

marcpopMSFT approved these changes Jul 18, 2024

View reviewed changes

Reimplement STJ change

9763f0b

Forgind force-pushed the stj-version branch from 5fa0ce6 to 9763f0b Compare July 18, 2024 22:28

Forgind requested review from a team, AntonLapounov, arunchndr, joperezr, sharwell and tmat as code owners July 18, 2024 22:28

Forgind removed request for a team, AntonLapounov, arunchndr, joperezr, lewing, maraf, pavelsavara, radical, sharwell, tmat and vijayrkn July 19, 2024 14:33

PR feedback

9fe4889

build-analysis bot mentioned this pull request Jul 20, 2024

Roslyn analyzer throws error AD0001 NullReferenceException dotnet/dnceng#3305

Closed

3 tasks

Merge branch 'main' into stj-version

3cf8751

Forgind commented Jul 22, 2024

View reviewed changes

eng/Versions.props Outdated Show resolved Hide resolved

rainersigwald reviewed Jul 22, 2024

View reviewed changes

eng/Versions.props Outdated Show resolved Hide resolved

Forgind force-pushed the stj-version branch from d571396 to 3cf8751 Compare July 23, 2024 18:47

Forgind added 5 commits July 23, 2024 14:47

Merge branch 'main' of https://github.com/dotnet/sdk into stj-version

2d84bf5

change base to toolset

bf21493

Back up to 8.0.4

091f0b4

VS has upgraded to STJ 8.0.4, so we can, too

Merge branch 'main' into stj-version

1a2fee1

expect 8.0.0.4

337965f

build-analysis bot mentioned this pull request Jul 29, 2024

Microsoft.NET.Build.Containers.IntegrationTests are pulling from Docker Hub #42026

Closed

marcpopMSFT approved these changes Jul 30, 2024

View reviewed changes

Forgind merged commit 3ab6945 into dotnet:main Jul 31, 2024

Forgind deleted the stj-version branch July 31, 2024 17:20

Youssef1313 mentioned this pull request Sep 11, 2024

Can no longer compile any project after upgrading from .NET 9.0 Preview 7 to .NET 9.0 RC1 #43339

Closed

Clean up STJ references Fixes #39902 #40645

Clean up STJ references Fixes #39902 #40645

Uh oh!

Conversation

Forgind commented May 2, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

ViktorHofer commented Jul 22, 2024

Uh oh!

Uh oh!

Uh oh!

Forgind commented Jul 29, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Forgind commented May 2, 2024 •

edited

Loading