While we contributed changes to NuGet to work with the Unified API support, there has not been a new release of NuGet, so we are evaluating how to get NuGet to recognize the new APIs. Any component that has not yet been converted by the author, will display a 32 bit only warning in the component store. For any included component, replace the current version with a new version from the Xamarin Component Store that supports the Unified API and do a clean build. ComponentsĪny component that you have included in your application will also need to be updated to the Unified API or you will get a conflict when you try to compile. The following considerations should be taken into account when converting an existing Xamarin.Forms project from the Classic API to the new Unified API if that app relies on one or more Component or NuGet Package. The project should build successfully once these old references are removed. Public class App : Application // superclass new in 1.3
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |