![]() The Xamarin docs say that you can use one of three code-sharing strategies: a Shared Asset Project, a PCL, or a. Little did we know that this would create days of headaches due to small bugs and undocumented use-cases. ![]() ![]() NET Standard is the direction Microsoft is pushing, we decided to give that a try. Using a Shared Asset Project was not really considered since it would require adding all files in our existing projects as links, one by one. It was time to migrate our shared class libraries to either PCLs or. However, we quickly found this wouldn’t work with Xamarin Forms. NET class libraries from Android without any modifications. Somehow, we got away with referencing our legacy. This isn’t supposed to be possible according to all docs I’ve seen those projects should have had to been Portable Class Libraries (PCLs). Our Xamarin Android project referenced some shared. ![]() Hopefully, at some point in the future we can re-write our Xamarin Android app to use the Xamarin Forms base we are building now. We already had a Xamarin Android app, but we decided to try writing an iOS app using Xamarin Forms instead of Xamarin iOS. Recently at Ocuvera, we faced the challenge of adding an iOS app to our offerings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |