❔ Project References Different SDK Versions: Visual Studio Fails, Rider Does Not?
So, we have a project, in which we have a shared project containing... Shared code.
The shared project has a reference to a sdk which is 9xxx
The projects that uses code from the shared sdk has a version of 8xxx
Visual studio fails to build, however Rider does not?
I read somewhere that rider resolves SDK version behind the scene?
I know the fix, but I am curious as too why Rider chooses to autoresolve version conflicts, especially when they typically signify a setup failure?
The shared project has a reference to a sdk which is 9xxx
The projects that uses code from the shared sdk has a version of 8xxx
Visual studio fails to build, however Rider does not?
I read somewhere that rider resolves SDK version behind the scene?
I know the fix, but I am curious as too why Rider chooses to autoresolve version conflicts, especially when they typically signify a setup failure?
