Found conflicts between different versions of "System.Diagnostics.DiagnosticSource" that could not be resolved
I am working with WinForm App targeting net461 framework. Unfortunately, this warning appeared in runtime error list :
Found conflicts between different versions of "System.Diagnostics.DiagnosticSource" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.
Adding to package.config does not helped :
<?xml version="1.0" encoding="utf-8"?>
<packages>
<package id="System.Diagnostics.DiagnosticSource" version="4.4.1" targetFramework="net461" />
</packages>
Does anybody have an idea about this?
The problem usually arises when different dependencies bring their own version of System.Diagnostics.DiagnosticSource assembly. It is true for any other assembly conflict as well.
The reason for such behavior lies in a faulty design of .NET Framework but also .NET Core dependency logic. The same warnings were quite often produced by .NET Core coreclr and corefx repo builds with only side effects being larger NuGet package containing all conflicting versions of assemblies and even complete frameworks.
The warning itself is benign and can be safely ignored. The only impact is that more packages will be imported by NuGet during the build.
- Sort program not working, not sure why
- Fast & accurate atan/arctan approximation algorithm
- What's the difference between strtok_r and strtok_s in C?
- How memory address for pointer to arrays is same as an element in 2D array?
- Which is the best way to suppress "unused variable" warning
- How to use ellipsis in c's case statement?
- How can I exclude non-numeric keys? CS50 Caesar Pset2
- Fast ceiling of an integer division in C / C++
- Is there an invalid pthread_t id?
- How to Implement Universal Setter/Getter Functions for Interrupt-Driven Variables in Embedded C?
- How does SIMD (avx) processing work? for example, if I want 10 32 bit floats how do i fit in a 256 bit avx vector?
- FDCAN problems on STM32G4
- How does the call macro enable mutual recursion between functions f and g in this Hanoi Tower implementation?
- Running test on Rocket core CPU - global variable initialized to 0 is unsuccessful, output wrong value instead
- Interacting with C arrays without knowing the size
- Combination of two strings
- Avoiding strcpy overflow destination warning
- carriage return by fgets
- How to use special characters in C?
- Why does 1.0/100.0 == 0.1/10.0 give True?
- Is it correct to compare pointers in C?
- Force free() to return malloc memory back to OS
- How can I print to standard error in C with 'printf'?
- What is the standard behavior of fread in C on Windows?
- How is strtok removing lines it shouldn't have access to?
- Using array as smart point in C
- Assigning string to malloced 2d char array not working as intended
- How to refactor repetition inside a Makefile?
- Why does an empty preprocessor command still evaluate to something?
- How to implement variable sized array within C struct