Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to update Portable Class Profile? #39

Closed
FObermaier opened this issue May 26, 2015 · 8 comments
Closed

Need to update Portable Class Profile? #39

FObermaier opened this issue May 26, 2015 · 8 comments

Comments

@FObermaier
Copy link
Member

Currently the GeoAPI/NTS/ProjNet stacks PCL projects are

  • compiled with .NETPortable,version=v4.0,profile=Profile147
  • packaged with portable-net403+sl5+netcore45+wp8+MonoAndroid1+MonoTouch1

Is this setting ok, or do we need to change that. Here is a list of what is currently possible:
http://embed.plnkr.co/03ck2dCtnJogBKHJ9EjY

@pauldendulk
Copy link
Member

BruTile uses Profile336 which includes Windows Phone 8.1.

Is it also an option to jump forward to a profile that includes .NET 4.5 and drop Silverlight and Windows Phone Silverlight. This add a lot of modern functionality. For NTS this may be too early.

@ghost
Copy link

ghost commented Jun 11, 2015

I would like to cast a vote to using at least Profile328.
Reasons

  1. This seems like the minimum target that users of Visual Studio 2013 can use, possibly solving mine and jcdekoning's issue.
    https://msdn.microsoft.com/en-us/library/vstudio/gg597391(v=vs.110).aspx
    I'm not sure what the minimum target will be for Visual Studio 2015 which is coming out in July. I'm installing 2015 RC now to check
    -- after installing, a lot of the profiles add support for Xamarin.Android, Xamarin.iOS.Unified and Xamarin.iOS
  2. I would like to be able to use GeoAPI, NTS, Proj.Net in a Universal Windows App :)

@FObermaier
Copy link
Member Author

We'll be releasing a new version of GeoAPI/NTS with PCL assemblies targeting Profile 328.

@DGuidi
Copy link
Contributor

DGuidi commented Jun 25, 2015

@FObermaier thanks felix, hope to be more helpful in next months

@FObermaier
Copy link
Member Author

We'll be releasing a new version of GeoAPI/NTS with PCL assemblies targeting Profile 336 in the next week.
For 328 we'd have to change some code that depended on portable-net403

@FObermaier
Copy link
Member Author

@cedricseah, @jcdekoning:
Could you please test GeoAPI.1.7.4-pre2 and NetTopologySuite.1.13.4-pre3 packages
The PCL TargetProfile is set to 336.

@ghost
Copy link

ghost commented Aug 11, 2015

Using Visual Studio 2013 Pro:

I am able to install GeoAPI 1.7.4-pre2 in a PCL project (targetting 336) using Nuget.
When I try to install NTS -Topology Suite 1.13.4-pre3, I get the following error message even though GeoAPI 1.7.4-pre2 is installed

Attempting to resolve dependency 'GeoAPI (≥ 1.7.4 && < 1.8)'.
Unable to resolve dependency 'GeoAPI (≥ 1.7.4 && < 1.8)'.

Using Visual Studio 2015 Pro:
No problem installing both packages in a Universal Windows App.

When installing NTS package in a PCL:
Unable to resolve dependencies. 'GeoAPI 1.7.4-pre2' is not compatible with 'NetTopologySuite 1.13.4-pre3 constraint: GeoAPI (≥ 1.7.4 && < 1.8.0)'.

@FObermaier
Copy link
Member Author

I am able to install GeoAPI 1.7.4-pre2 in a PCL project (targetting 336) using Nuget.
When I try to install NTS -Topology Suite 1.13.4-pre3, I get the following error message even though > GeoAPI 1.7.4-pre2 is installed

Attempting to resolve dependency 'GeoAPI (≥ 1.7.4 && < 1.8)'.
Unable to resolve dependency 'GeoAPI (≥ 1.7.4 && < 1.8)'.

I know that, I just don't know how to deal with prerelease packages in the nuspec version constraints. You can install it anyhow by adding the -ignoredependency flag.

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

No branches or pull requests

3 participants