NET 4.7 as an explicit target, then thanks (and sorry to discard this issue as a duplicate of #280) and so I'm re-opening the issue on that basis. If this is a kind reminder that the dependency should be removed the day we decide to add. If you're having the same issue then this is a duplicate but I don't think that's your case. Let me ask you, how is this bothering you today? In #280, the issue was compilation errors for people. MoreLINQ doesn't have an explicit target for 4.7 so our only way to solve the issue is to exploit, as you put it, the kind favour from Microsoft.
The issue I see with adding the 4.7 target to MoreLINQ is that anyone wanting to build and contribute to the project will also need to have 4.7 installed, which is setting the bar pretty high for what seems to be an artificial requirement.
This should really be solved by the System.ValueTuple package instead of every dependent having to do it. Net 4.7, the right thing to do is target 4.7 and remove the Correct but as I said in the following comment in #280: Net 4.7, the right thing to do is target 4.7 and remove the dependency. Net 4.7 and say it doesnt need the dependencies.Īnd so, no you arent doing the right thing for. Microsoft was just nice enough to say, hey we fix it - that they can work together (again rendering the NuGet Package useless since it just redirects) - instead of telling every developer you need to explicitly target. You simply dont need the NuGet Package System.ValueTuple in. Net 4.7 are both in use, rendering the NuGet Package System.ValueTuple useless. Microsoft updated the NuGet Package so that it will redirect to use the mscorlib if System.ValueTuple AND. Net 4.7 internally already has the System.ValueTuple in-build into the mscorlib and the NuGet Package providing the same namespaces/classes with an external DLL.īoth of them just simply cannot work together and you would result in having the same classes twice. Net 4.7 and the NuGet Package System.ValueTuple inside a single project. Sorry, but its more like you need to read it once more.
0 kommentar(er)
