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
When including Serilog.Settings.Configuration 3.0.0-dev in a .NET Framework 4.7.1 (net471) project, NuGet resolves the net451 assembly from the package instead of the netstandard2.0 assembly. This pulls in Microsoft.Extensions.Options.ConfigurationExtensions >= 1.1.2 rather than >= 2.0.0 as defined in the netstandard2.0 assembly. This causes a package conflict in our solution with another project that requires v2.0 of that package. NuGet resolves this dependency to v1.1.2:
There was a conflict between "Microsoft.Extensions.Options.ConfigurationExtensions, Version=1.1.2.0, Culture=neutral, PublicKeyToken=adb9793829ddae60" and "Microsoft.Extensions.Options.ConfigurationExtensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60".
"Microsoft.Extensions.Options.ConfigurationExtensions, Version=1.1.2.0, Culture=neutral, PublicKeyToken=adb9793829ddae60" was chosen because it was primary and "Microsoft.Extensions.Options.ConfigurationExtensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60" was not.
References which depend on "Microsoft.Extensions.Options.ConfigurationExtensions, Version=1.1.2.0, Culture=neutral, PublicKeyToken=adb9793829ddae60" [C:\Users\AlastairSmith\.nuget\packages\microsoft.extensions.options.configurationextensions\1.1.2\lib\netstandard1.1\Microsoft.Extensions.Options.ConfigurationExtensions.dll].
C:\Users\AlastairSmith\.nuget\packages\microsoft.extensions.options.configurationextensions\1.1.2\lib\netstandard1.1\Microsoft.Extensions.Options.ConfigurationExtensions.dll
Project file item includes which caused reference "C:\Users\AlastairSmith\.nuget\packages\microsoft.extensions.options.configurationextensions\1.1.2\lib\netstandard1.1\Microsoft.Extensions.Options.ConfigurationExtensions.dll".
C:\Users\AlastairSmith\.nuget\packages\microsoft.extensions.options.configurationextensions\1.1.2\lib\netstandard1.1\Microsoft.Extensions.Options.ConfigurationExtensions.dll
References which depend on "Microsoft.Extensions.Options.ConfigurationExtensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60" [].
F:\code\platform\src\ServiceHost\bin\Debug\netstandard2.0\CH360.Platform.ServiceHost.dll
Project file item includes which caused reference "F:\code\platform\src\ServiceHost\bin\Debug\netstandard2.0\CH360.Platform.ServiceHost.dll".
F:\code\platform\src\Queue.Rabbit\bin\Debug\netstandard2.0\CH360.Platform.Queue.Rabbit.dll
F:\code\platform\src\ServiceHost\bin\Debug\netstandard2.0\CH360.Platform.ServiceHost.dll
The text was updated successfully, but these errors were encountered:
If your issue could be fixed by NuGet packaging changes, I assume it would create the opposite problem for others. Sounds pretty thorny (but I'm not exactly a NuGet packaging expert).
When including Serilog.Settings.Configuration
3.0.0-dev
in a .NET Framework 4.7.1 (net471
) project, NuGet resolves thenet451
assembly from the package instead of thenetstandard2.0
assembly. This pulls in Microsoft.Extensions.Options.ConfigurationExtensions >= 1.1.2 rather than >= 2.0.0 as defined in thenetstandard2.0
assembly. This causes a package conflict in our solution with another project that requires v2.0 of that package. NuGet resolves this dependency to v1.1.2:The text was updated successfully, but these errors were encountered: