nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Use of ArcGIS Runtime SDK .NET in Xamarin app with PCL config ?

EricDUCOS1

Hi,

We are working on a new Xamarin project that would include ArcGIS components.

We followed Microsoft recommendation saying that it is better to use the Xamarin model with Portable Library (PCL), not shared components.

But I do not see how to integrate ArcGIS NuGet package in such a project. I get every time an error saying that I try to to install a package that target .NETPortable but that the package is not compatible with such target...

Please tell me what is the solution...

Probably a version of this Runtime SDK should be supplied supporting PCL ?

Regards.

Eric.

Encontre mais publicações marcadas com

Accepted answers

All comments

alehmann

There are technical aspects that hinder Esri from providing the Runtime in a PCL-compatible way. Therefore, only shared projects are supported (at least that's what I've heard from them).

AnttiKajanus1

That is correct. Unfortunately there are technical limitations that prevents us to deliver the API to PCL.

deleted-user-Ohz6rwd1kavx

Is PCL support something that we can expect in a future release?

FWIW, this is the message I see when I try to install Esri.ArcGISRuntime.Xamarin.Forms for a Portable Class Library project:

Could not install package 'Esri.ArcGISRuntime.Xamarin.Forms 100.0.0'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.6,Profile=Profile44', 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.

AnttiKajanus1

Hi,

As mentioned in the earlier post, we cannot support PCL due it's technical limitations.

SomeGISGuy

We are actively researching supporting .NET Standard 2.0+ in the future, and this _might_ just be possible now. However it would require some breaking changes and dropping support for older platforms, but I'm hoping we'll be able to go there, but not something we can promise at this point, nor give a timeline for.

So if we do this it would be out in the future. Until then shared projects is the way to go for Xamarin + ArcGIS Runtime.

deleted-user-Ohz6rwd1kavx

Thanks very much for the info. Looking forward to more goodness in Palm Springs.

brianbullas

This made me /sad to learn that PCL's aren't supported. I found this out the hard way today. The whole point of Xamarin forms is to have one code base delivered to multiple platforms. But by limiting us to Shared libraries (instead of portable libraries), we can't even add a service reference or a nuget package to the shared library...thus totally limiting us to what we can do. PCL is the way of the future Xamarin / Crosss platform applications.

totally frustrating.

SomeGISGuy

The whole point of Xamarin forms is to have one code base delivered to multiple platforms

A shared project still gives you one code base - it just doesn't give you one binary

we can't even add a service reference or a nuget package to the shared library

You would add the reference to each project, but still write the code in the shared library

JamieBurmeister

WHEN WILL THERE BE A PCL VERSION?

SomeGISGuy

There are no plans to support PCLs. We are hoping to support .NET Standard in the future, but please see my response here regarding that: https://community.esri.com/message/711402-support-for-net-standard#comment-711590

EricDUCOS1

Hi everybody,

I am at the origin of this thread and see that I am not alone to request the evolution, but it seems that there is no plan to get ArcGIS component work with standard Xamarin Forms project based on PCL.

But....

With some test and hours, we found an acceptable solution that permit to work with ArcGIS component in such projet. We created a standard XamarinForms PCL project and added a Shared project in which we focused all code using ArcGIS library. And we defined some Interface that permits to the PCL project to get playing with ArcGIS component. In the Shared Library we define some class that implements Interface. And we get the class in the PCL project using Dependency.

For exemple, suppose you have this definition in your XAML page

<ContentView x:Name="_mapContainer" Grid.Row="0"/>

Then you define an interface IMapView

You define a ContentView in your shared project that contains the MapView control of ArcGIS and you make the implemntation file of this view implementing the IMapView interface.

Then in your PCL project, you get instance of this class by this instruction

IMapView mapView = DependencyService.Get<IMapView>(DependencyFetchTarget.NewInstance);

_mapContainer.Content = mapView as ContentView;

This seems to work in our case.

Eric.

CharlesMoszkowicz

Hi Eric,

I would also like to use the ESRI Component with a PCL project. Could you explain a little bit more how did you manage to do that ? I've already created a Arcgis Runtime shared project (in the same solution of the PCL). Can you share some code please, specifically the interface in the PCL and the code in the Shared Project.

Thanks

SomeGISGuy

At this point PCL is essentially dead, and getting replaced by .NET Standard.

I think you're better off creating a multi-targeting project instead. That'll set you up great for moving to .NET Standard, while having a single project output you can share.

https://oren.codes/2017/01/04/multi-targeting-the-world-a-single-project-to-rule-them-all/

SomeGISGuy

...I just pushed a sample up on GitHub that demonstrates multi-targeting to help you get started: https://github.com/Esri/arcgis-runtime-demos-dotnet/blob/master/src/MultiTargeting

EricDUCOS1

Hi,

There seems to be a problem with my mail box, so the answer did not get into the thread...

I republish my answer below:

-------

Hi Charles,

Sorry not to have given answer before…

First, I think that Morten given some part of answer just because now when you create a Xamarin Project, PCL project is replaced by .NET Standard project. But I did not test if ArcGIS Runtime SDK .NET is compatible with Standard (I read a thread about that but did not verify…)

If you already have a Xamarin with PCL project, you can do something like we have done to arrange the things…

In your Shared project you create a Xamarin ContentView with the MapView control. In the code behind, you add an interface like this…

public partial class MapPageView2 : ContentView, IMapView

IMapView defines some method that you will use to initialize Map and returning some data from ESRI SDK like layers, or to react to some event like touch .

In each specific projet for Android, iOS or Windows, you use DependencyService to register the class defined in the shared project like for example:

DependencyService.Register<IMapView, MapPageView2>();

In he PCL project you define a new Xamarin XAml page tha will contains a ContentView control like:

(here my control belongs to a grid…)

And somewhere in the code behind of this page, you make the binding….I discovered that this code has to be put in different place according to the plateform…

For UWP, this is in the constructo:

if (Device.RuntimePlatform == Device.UWP)

{

var mapView = DependencyService.Get<IMapView>(DependencyFetchTarget.NewInstance);

mapView.SetMap(); // This method defined in the interface and implemented in the class in the shared projet use configuration to load a WebMap in the map control

_mapContainer.Content = mapView as ContentView;

}

For Android, the same code has to be placed in the OnAppearing…

This is not really good coding, but it works…I really hope that the new Standard platform used by new Xamarin project will work without shared project for ArcGIS .NET SDK.

I hope that my explanations will help you in some way.

Eric.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.