How can I use .NETStandard libraries on a Xamarin project. I have already made a try to create a portable library targeting .NETStandard 1.6.
this is the project.json of portable library
This is the properties of portable library
Any suggestions?
I recently faced a similar problem and was able to solve it by recreating the .net standard library as outlined here in Orens Blog.
He even has a sample on github which is a great starting point.
Related
We've recently started a project with the Virtual Assistant Template 1.0.1, and I wonder if it is safe to target the solution to net5.0 since we have some libraries that use this latest .NET GA release.
Currently, the VA template references the Bot Framework SDK 4.9.3. Any requirements on the SDK version?
I've done a couple of tests to confirm. The project compiles, and I can't see any errors. However, I'm looking for some confirmation from the community.
There are no obvious problems with targeting .NET 5. But if you'd like to be safe, you should go with the version the samples are using:
<TargetFramework>netcoreapp3.1</TargetFramework>
Hi when i am going to create new xamarin forms app I'm not able to see Protable Class Library in the Sharing Code Strategy options in VS 2017 .enter image description here
Please help me in this
That's the expected behavior, it's no longer possible to create a PCL library with Visual Studio 2017 as they've been replaced by .NET Standard libraries, see here for more details.
Also, the roadmap and the comparison with PCL profiles is available here, so you can determine the right .NET Standard version for you depending on your target framework and the APIs you need to place in the shared library.
.NET Standard libraries are the replacement for Portable Class Libraries. They allow you access to more of the framework than pcl did. You can still manually create a PCL project and reference it in a Xamarin app if you would like to use PCLs in new mobile apps with Xamarin.
I downloaded ArcGIS Runtime SDK for Xamarin (Quartz Beta).
On installing it out of the box in portable project I get following error :
Could not install package 'Esri.ArcGISRuntime.Xamarin.Forms
100.0.0.1369-beta'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile7
I tried to change the profile number but it doesn't seem to work. How should I proceed?
The sample code from their github project shows that they set up their projects using a shared code approach rather than a Portable Class Library. I'm not sure they designed their library with PCL support in mind.
In the beta forums, an esri employee answered this with regards to whether the SDK could support PCL:
Unfortunately PCL isn't possible for the Runtime due to some of the native dependencies. We recommend using shared projects to share the code you otherwise would have put in a PCL.
Recently Xamarin announced support for NetStandard (see https://releases.xamarin.com/stable-release-cycle-7-service-release-1/) and the recently shipped Entity Framework Core supports NetStandard. There was a recent issue with the SQLite.Native package that has been resolved (see https://github.com/aspnet/EntityFramework/issues/4269) but when I build the Android version of a Xamarin Forms application it appears it does not include all the assemblies in the output that are needed by the Entity Framework and therefore the application will not run and crashes on the first line of EF code to retrieve data. The UWP version appears to work just fine so this seems like an issue with Android (possibly iOS too).
Has anyone run into this and know a way around it so that the compiled Xamarin Forms Android application will run using Entity Framework Core to access a SQLite database?
Thank you in advance.
Here are the steps you can follow.
Create a Xamarin.Forms project.
Convert the PCL project's properties to .NET Standard 1.3
Install Entity Framework Core and other EF Core stuffs
I have prepared a small hello world project at Github Here.
need to use -linkskip to inform compiler not to remove references.
I have a project which greatly depends on ServiceStack, unfortunately the V4 releases, which includes PCL release for most platforms(especially after forking out for a Xamarin Licence), is just way out of my price range as an ISV. I have cloned the MvvmCross code but before I start messing around I would like to know what pitfalls I could run into when attempting to create a Non PCL based version compatible with the platforms I target (Currently Xamarin.Android, WPF and WinRT). The idea would be to able to reuse the code for the WPF project to build Android and WinRT clients.
Does anyone have any pointers?
I don't think there is any problem or pitfall with what you are describing - and I don't think you'll need to fork the MvvmCross source.
You should be able to build your apps as native code, and should then be able to reference the MvvmCross PCL libraries directly from the native libraries you are building - you don't need to rebuild MvvmCross to do this. Plenty of people already use MvvmCross using "file linking" rather than PCLs - it's not the default setup encouraged by the Nuget packages, but it still works fine.