Skip to content
This repository has been archived by the owner on Sep 3, 2019. It is now read-only.

Unable to install on VS 2015 Xamarin iOS project use NuGet #263

Open
nhaizere opened this issue Aug 7, 2015 · 11 comments
Open

Unable to install on VS 2015 Xamarin iOS project use NuGet #263

nhaizere opened this issue Aug 7, 2015 · 11 comments
Assignees
Labels
Milestone

Comments

@nhaizere
Copy link

nhaizere commented Aug 7, 2015

Could not install package 'OsmSharp 4.2.0.723'. You are trying to install this package into a project that targets 'Xamarin.iOS,Version=v1.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

Looks like target framework xamarinios1 wasn't included. Is there any solution to install this package?
Btw dependency protobuf-net 2.0.0.668 can't be installed by same reason.

@xivk xivk self-assigned this Aug 18, 2015
@xivk xivk added the bug label Aug 18, 2015
@xivk xivk added this to the OsmSharp v4.4 milestone Aug 18, 2015
@xivk
Copy link
Contributor

xivk commented Aug 19, 2015

Note: This is an issue with the Nuget packages and Unified API.

@xivk xivk closed this as completed in fa961ba Aug 19, 2015
@xivk
Copy link
Contributor

xivk commented Aug 19, 2015

Updated according to the information found here:

http://developer.xamarin.com/guides/cross-platform/advanced/nuget/

Can you verify?

@nhaizere
Copy link
Author

@xivk looking at your commit you've just changed targets. But that type of project references different lib types. In your OsmSharp.iOS.UI Assembly its monotouch (http://i.imgur.com/S0baszN.png) but that new Xamarin iOS type project based on Xamarin.iOS Assembly so its definitely not a fix.

@xivk xivk reopened this Aug 25, 2015
@pauldendulk
Copy link

I did the Xamarin.iOS Unified API upgrade for a larger project and it was actually quite a lot of work. Code changes as well. The automatic upgrade of Xamarin Studio caused the most work. Don't use it.

@xivk
Copy link
Contributor

xivk commented Dec 2, 2015

@pauldendulk Thanks!

This commit should already have added support for unified API:

a2508b8

I'll check what happens in the build process with the result.

@pauldendulk
Copy link

Using NuHelper with this command:
nuhelper shortFrameworkName .NETPortable,Version=v4.0,Profile=Profile147
Results in this string for the .nuspec:
portable-net403+sl50+win+wp80+Xamarin.iOS10+MonoAndroid10+MonoTouch10
I expect this to solve the problem.

@pauldendulk
Copy link

It is also be possible to generate the nuget package directly from the csproj
> nuget spec osmsharp.ui.csproj -IncludeReferencedProjects -version 0.0.1-pre
The more automation the better. Not sure when to use which (generating from csproj or nuspec).

@xivk
Copy link
Contributor

xivk commented Dec 8, 2015

The protobuf-net dependency also doesn't install using Nuget on a fresh new 'Xamarin.iOS'. What a mess has this become all of a sudden.

@mgravell
Copy link

mgravell commented Dec 8, 2015

@xivk if there is a particular nuget target / moniker I should be using, let me know...

@ahmedalejo
Copy link

@mgravell ,

NuHelper.exe shortFrameworkName .NETPortable,Version=v4.0,Profile=Profile136
portable-net40+sl50+wp80+win+MonoAndroid10+MonoTouch10

the above indicates that you(protobuf-net) already support MonoAndroid10+MonoTouch10

please make it happen shoud be as easy as renaming the nuspec, i hope

@Fox4148
Copy link

Fox4148 commented Dec 19, 2016

Find out how to install successfully, just go to the packages that failed (protobuf-net) and install the latest version. :) Enjoy

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants