You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We transitively include both MathNet.Numerics and the legacy MathNet.Numerics.Signed packages in RDMP, both of which provide version 5.0.0 of MathNet.Numerics but only one as an (obsolete) "strong name" signature. This causes build warnings, upsetting downstream projects using bits of RDMP (like SmiServices)....
To Reproduce
Steps to reproduce the behavior:
Build RDMP, look at warnings.
Expected behavior
Build should be warning free.
dotnet build --use-current-runtime -p:Platform=x64 --configuration Release --verbosity quiet --nologo
/usr/share/dotnet/sdk/8.0.301/Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3243:
No way to resolve conflict between "MathNet.Numerics, Version=5.0.0.0, Culture=neutral, PublicKeyToken=cd8b63ad3d691a37"
and "MathNet.Numerics, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null". Choosing "MathNet.Numerics, Version=5.0.0.0,
Culture=neutral, PublicKeyToken=cd8b63ad3d691a37" arbitrarily.
[/home/runner/work/SmiServices/SmiServices/src/common/Smi.Common/Smi.Common.csproj]
The text was updated successfully, but these errors were encountered:
Describe the bug
We transitively include both
MathNet.Numerics
and the legacyMathNet.Numerics.Signed
packages in RDMP, both of which provide version 5.0.0 ofMathNet.Numerics
but only one as an (obsolete) "strong name" signature. This causes build warnings, upsetting downstream projects using bits of RDMP (like SmiServices)....To Reproduce
Steps to reproduce the behavior:
Expected behavior
Build should be warning free.
The text was updated successfully, but these errors were encountered: