Search Issue Tracker

By Design

By Design in 6000.6.X

Votes

0

Found in

6000.5.0b3

6000.6.0a2

Issue ID

UUM-139823

Regression

Yes

CS1705 error is thrown when BCLExtensions assemblies override higher-version NuGet dependencies

Scripting Buildtime

-

Reproduction steps:
1. Open the attached “BugRepro” project
2. Observe the Console window

Actual result: error CS1705 is thrown
Expected result: No errors are thrown

Reproducible with: 6000.5.0a7, 6000.5.0b4, 6000.6.0a2
Not reproducible with: 6000.0.73f1, 6000.3.13f1, 6000.4.2f1, 6000.5.0a6

Reproducible on: Windows 11
Not reproducible on: No other environment tested

Full error:

  • error CS1705: Assembly 'ReflectorNet' with identity 'ReflectorNet, Version=4.1.0.0, Culture=neutral, PublicKeyToken=null' uses 'System.Text.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' which has a higher version than referenced assembly 'System.Text.Json' with identity 'System.Text.Json, Version=8.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.

    We know you were able to previously use NuGet type packages in this manner but this is not an official supported feature of Unity. Recently we made some changes that resulted in us requiring System.Text.Json for some upcoming features. However, we cannot support the co-existence of two versions of the same package and need to stay complient with our version of .Net (version 8) which is why your added version 10 of System.Text.Json get's automatically invalidated.

    I am sorry, but we unfortunately cannot fix this as this is the intentional behaviour.

  2. Resolution Note (6000.6.X):

    Thank you for reporting a bug to Unity.

    After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.

    We know you were able to previously use NuGet type packages in this manner but this is not an official supported feature of Unity. Recently we made some changes that resulted in us requiring System.Text.Json for some upcoming features. However, we cannot support the co-existence of two versions of the same package and need to stay complient with our version of .Net (version 8) which is why your added version 10 of System.Text.Json get's automatically invalidated.

    I am sorry, but we unfortunately cannot fix this as this is the intentional behaviour.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.