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
Unfortunately we don't use AutoGenerateBindingRedirects for these, because that doesn't generate an FSHarp.Core binding redirect, which is required for most type providers to work.
So we have to do this manually for now unless we find someway to automate this
Yeah ... we are in actual dll hell now. I have spent most of the last two days trying to get our build working again. which included reverting back to System.Collections.Immutable 1.2.0.
Parts of vs require and deploys 1.2.0, roslyn is build using 1.2.1, VS has binding redirects back down to 1.2.0.
Anyway I think this will be taken care of by: #2675 which was supposed to just add sourcelink support, but now kind of fixes our current dll hell issues.
As a side note: when code reviewing we need to be especially careful when looking at changes to dependent packages.
I am actually a bit mystified why the CI is continuing to work, although I suppose it may be that it reuses images, and they have parts of previous package downloads.
Our internal microbuild has failed nightly for the last 4 nights, and I definitely see failures on all of my machines.
I am considering adding a git clean -fxdq to our CI.
The reason will be displayed to describe this comment to others. Learn more.
Just a reminder that when using nuget packages, paket actually does a good work at generating those redirects (related to nuget packages you are pulling) for you.
I've spent too much time with conflicts and binding redirects, msbuild or nuget are just hopeless in helping the developer do the right thing in this context.
When I switched to paket at my work, it simply relieved me from that problem, I don't face binding redirects issues, or only in case I'm pulling dependencies outside of nuget eco system (which is very seldom).
This is the only fsharp repository which is not using paket so maybe we could do some harmonization?
The reason will be displayed to describe this comment to others. Learn more.
Looking at the diff, paket would solve the one for System.Collections.Immutable, and if we made a nupkg of FSharp.Core for consumption in other projects, it could also write that one automatically.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unfortunately we don't use AutoGenerateBindingRedirects for these, because that doesn't generate an FSHarp.Core binding redirect, which is required for most type providers to work.
So we have to do this manually for now unless we find someway to automate this