![]() I do hope to provide an update on this in the very near future - it should work 'out of the box' soon. I personally deliver MvvmCross (and a lot of apps that use MvvmCross) using PCLs - and have done for the last 6 months - but there is some setup pain involved in this currently. This situation is changing 'very soon' now with Xamarin adopting full PCL support - see and listen to Net4.5, WP, WinRT and Xamarin.Android - but not current against Xamarin.iOS. It is also currently possible to use the output binary assemblies across. Xamarin Visual Studio Enterprise 17.0.192 Full Patch adalah sebuah software yang dapat anda gunakan untuk membuat dan mengembangkan berbagai macam aplikasi di berbagai platform seperti Android, iOS, Mac, dan juga Windows. Net4.5, WP, WinRT, Xamarin.Android and Xamarin.iOS It is currently possible to use Portable Library Projects - e.g. So is this the only option? Or is there any way to have a true single class (model) library across all platforms, including Microsoft and Xamarin? ![]() Which I have tried and works - but it seems a hack. 'There is no additional functionality that is supported by the target frameworks you have selected'Īfter some research, I discovered that the only way Xamarin suggest to share code is to use separate projects with linked code files (so in effect, a pseudo-single code base. I can check Monotouch (Xamarin) as a supported platform here (where Windows phone, Windows store, etc are already checked), but it won't let me save. So I tried to change the model library's properties instead - maybe I can do something there. Except I can't, as the Xamarin iOS project needs to support Monotouch (and I can't change it to anything else from the GUI anyway). 'The current project's target framework is not compatible with that of the Portable Library project'.Īnd it suggests I change the target framework in the project properties. When I added the reference again, I was greeted by a different error: ![]() Seemed to be exactly what I needed - but no. I found a post here which suggested a fix that forced Visual Studio to detec the Monotouch (Xamarin) framework as supporting Portable Library Projects. Strange - as I thought this would be a scenario that would be supported. 'The current project does not support references to Portable Library projects'. When I first added a reference to my model class library to my Xamarin.iOS project (in Visual Studio), I was greeted by the error: My initial assumption was that I would be able to utilise this model library as I do with the other projects - however, I've since realised this this isn't the case. However, I've recently started experimenting with Xamarin - specifically the iOS functionality (with a view to moving onto Android later). This architecture works fine and without any issues. I've currently built a service layer and API which I'm consuming from an ASP.NET website, Windows Phone app, and a Windows 8 metro app - the key to all of them being a project containing model classes which is a portable class library project, and is shared as a reference between all of them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |