Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[WIP] Add proper versioning of MonoAndroid framework. #2427
So far no versioning for the MonoAndroid framework has been handled. However, I've been running into the case of different version constraints on transitive dependencies depending on the MonoAndroid framework version. As an example (and actually the concrete case I'm running into) take the nuspec of Xamarin.Forms.
In my case I'd like to update the Xamarin.Android.* packages to a higher version. As a first step, and what worked pretty good and straight forward so far, I implemented proper versioning of the MonoAndroid framework. This is what this PR currently contains.
However, even with the proper MonoAndroid framework version handling paket still is not able to resolve the following
From what I understood by reading the latest pull requests is that this involves framework restriction handling and has been refactored quite a lot in the last months.
I'm currently wondering if this kind of behavior is actually possible, and if so, at which part of the code I'd have to look to be able to understand its mechanism and maybe come up with a possible solution. Any hint and help is much appreciated!
Thanks a lot in advance, also for all the past work on paket which really is a joy to use!
Let me know if you need help.
Thanks for the hint! I wont be able to touch this during the week-end, but I should have updated test-cases and final modifications ready during next week. I've aleady been using paket with those modifications in our solution with the desired results, so I think I'm on the right way here.
Looks very good! If the 4.03 is not a bug (because the mabuild condition should be correct) then it lgtm