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; } } }

Xamarin.Forms - Are PCL projects supported?

CristianMadularu

Hi,

I recently started testing the Esri-ArcGIS set of libraries in some Xamarin Forms mini test projects. My tests looked promising which is why I started porting some of the code to one of our main Xamarin Forms solutions.

This solution is PCL based (vs shared).

I was not able to find a nuget package that would allow me to target the PCL project (where my pages using the MapView control would be).

Any suggestions?

Thank you,

Cristian

Encuentra más publicaciones etiquetadas con

Accepted answers

SomeGISGuy

PCLs are not supported. You need to use the shared Xamarin.Forms project template.

All comments

CristianMadularu

The reason I am avoiding using shared is the unit testing support. I want to be able to be able to unit test as much a possible.

Now, with the imminent release of .net standard 2.0, I converted my PCLs to standard, but still, I want to avoid shared for the reason mentioned above.

Thanks,

Cristian

PS: Sorry for the late reply.

SomeGISGuy

I understand the need for also supporting PCL, but we just can't support it the way PCLs are limited today.

We are considering supporting .NET Standard 2.0 in the future, as this looks to be resolving some of the limitations that PCLs are adding.

> If I may suggest, supporting PCL should not be complicated

True PCL isn't necessarily complicated, but in this case we're hitting "impossible", or we'll be creating an API that would be detrimental to developer ease of use. We chose to favor an easy to use API over a bunch of abstraction levels.

> Most large applications would not use shared projects

I'm curious why you are so much against shared over PCL, or what this statement is based on? You're still able to share code in a single project. Yes it creates a binary per platform, and you reference a project over a binary, but for the most part users use project references, and at the same time you'll never hit the "PCL Wall" and can always add #if-def in a few platform abstraction methods. I understand you don't get a common library binary .dll you can reference, but you would still be able to create a single nuget .nupkg you can reference in all your projects.

CristianMadularu

Hi Morten,

Thank you for the quick reply.

I believe that to be a severe limitation. Most large applications would not use shared projects. They would be PCL based. There are reasons for that, but, probably one of the most important one would be the better unit testing support the PCL projects offer. Also, it is also likely that potential map consumers may want to add the Esri map into their already exiting PCL based projects.

If I may suggest, supporting PCL should not be complicated. Behind the scenes you would still have platform specific implementations but you would need to abstract the implementation and then have some initialization code in the platform specific project. (Similar to the way the Map is abstracted in Xamarin Forms).

In my case, after some digging, I was able to use the ArcGIS map in a project based on a PCL template using some IOT (Unity in my case) magic

Thank you,

Cristian

SomeGISGuy

PCLs are not supported. You need to use the shared Xamarin.Forms project template.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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