Mvvmcross: Can't update MvvmCross.Binding to 4.2.1 on OS X
When trying to update the nuget-packages to 4.2.1, I get the following error on the binding-package:
Updating MvvmCross.Binding...
Attempting to resolve dependency 'MvvmCross.Core (≥ 4.2.1)'.
Attempting to resolve dependency 'MvvmCross.Platform (≥ 4.2.1)'.
Attempting to resolve dependency 'System.Collections.Concurrent (≥ 4.0.12)'.
'System.Collections.Concurrent' already has a dependency defined for 'System.Runtime'.
Downloading System.Collections.Concurrent 4.0.12...
'System.Collections.Concurrent' already has a dependency defined for 'System.Runtime'.
SimonSimCity
All 12 comments
I guess this is somehow related to #1385 ...
SimonSimCity
on 6 Jul 2016
Use a Nuget client which supports the new dependency systems.
martijn00
on 6 Jul 2016
System.Collections.Concurrent requires a recent version of NuGet package manager to install. Update it.
As for Xamarin.Studio, if you are using that, this will only work for a newer Alpha version, which allegedly supports this. Complain to Xamarin that NuGet package manager has been neglected in Xamarin.Studio, it is not our fault it sucks.
Cheesebaron
on 6 Jul 2016
I've already updated. Isn't NuGet 3.3.0.212 good enough? Tried it on the command line on OS X ...
SimonSimCity
on 6 Jul 2016
There is no System.Collections.Concurrent for profile 259.
You should fix the MvvmCross.Binding for that profile.
On profile 111 it works fine. Sticking on 4.2.0 for now.
drungrin
on 7 Jul 2016
Using a version of nuget which isn't supported by Xamarin Studio (unless you're on alpha) really limits the amount of people who can use this release...
It kinda reminds me of the release you guys did a little while back that would only compile if you were on a beta version of mono...
Did this change really need to be done right now?
petermajor
on 7 Jul 2016
@petermajor: Yes. Otherwise we couldn't release because the project couldn't build.
Also, Xamarin Studio has had its NuGet package manager neglected for ages, we can't wait around till someone at Xamarin gets the time to work on it.
@drungrin Profile 259 contains Silverlight stuff, we are slowly phasing that stuff out, you should consider doing it too.
Cheesebaron
on 7 Jul 2016
The pcl issue I mentioned happened within visual studio 2015, latest nuget. It doesn't install on pcl259.
Enviado do Outlook Mobile
On Thu, Jul 7, 2016 at 5:26 AM -0300, "Tomasz Cielecki" [email protected] wrote:
@petermajor: Yes. Otherwise we couldn't release because the project couldn't build.
Also, Xamarin Studio has had its NuGet package manager neglected for ages, we can't wait around till someone at Xamarin gets the time to work on it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
drungrin
on 7 Jul 2016
@drungrin Right because 259 supports silverlight. Since MvvmCross doesn't anymore you need to remove silverlight from your profile.
kjeremy
on 7 Jul 2016
And some wiki entries, like
https://github.com/MvvmCross/MvvmCross/wiki/Tip-Calc---The-Core-Project
which explicitly states about the profile 259.
drungrin
on 7 Jul 2016
No one have idea for stable xamarin studio nuget System.Collections.Concurrent issue? Using alpha software is very danger for real world applications.
ernesto
on 7 Jul 2016
@drungrin the statement about Profile 259 is from September 2014. Things have changed a lot since then.
Cheesebaron
on 7 Jul 2016
Related issues
ehuna
·
3Comments
kenigj
·
5Comments
merckxite
·
4Comments
iqbalmineraltown
·
3Comments
StephenBeirlaen
·
4Comments
Most helpful comment
There is no System.Collections.Concurrent for profile 259.
You should fix the MvvmCross.Binding for that profile.
On profile 111 it works fine. Sticking on 4.2.0 for now.