Hello Xamarin developers!
Now I am facing a couchbase.lite problem to integrate in Xamarin.forms ios project.
it crashes the app when link behaviour is "Link Framework sdks only", but "Don't link".
You know to reduce ipa size, we have to choose the "Link Framework sdks only".
I want your opinion.
thanks.
Yes, that is very serious problem, I had the same issue, so I insisted to use "don't link" and submitted to store.
I guess that is the Xamarin issue now. will be updated soon.
You can downgrade Xamarin version, or simply you can change your lite form couchbase.lite to sqlite.
sqlite also supports mvvmcross for xamarin.
it's package name is sqlite.net-pcl to find in nuget packages.
Related
I'm currently developing a little project, i've bought a "smart lock" with works with Bluetooth and uses an open platform called TTLock. The resources are here: https://open.ttlock.com/doc/userGuide
The idea is to create my own App to control this "smart lock" using the methods created by TTLock.
The web page gives SDK resources for Android and IOS, but i want to program my App in Xamarin.Forms. My question is, can I "add" the Android SDK and the IOS SDK to my Xamarin.Forms solution and work with that methods, or i have to program first in Android Studio and later in an IOS IDE?
Thank you so much for your time and your responses. I'm learning about programming APPs on IDE, so all knowledge will be appreciated.
My question is, can I "add" the Android SDK and the IOS SDK to my Xamarin.Forms solution and work with that methods,
The answer of the first question is Yes. You could refer to Binding a .JAR document to use it in Android, and refer to Binding iOS Libraries document to use it in iOS.
or i have to program first in Android Studio and later in an IOS IDE?
The second question is depends on you. You will not need to use native IDE to do that.
For Android, there are two ways to get the native library:
Using Android Studio to download it
Going to Source repository website to download it
First method, I think you already know that, from the document you will find the sample steps:
The Second method, the shared document is chineses language. Therefore, you could find the source repository website here: https://maven.aliyun.com/mvn/search, and search by typing tongtonglock you will see the navtive libraries as follows. Then you can pick one to download.
For iOS, you could refer to its sample link to get the framework.
Is Xamarin.Forms considered a simple sum of Xamarin.Android and Xamarin.IoS with a shared code library wrapper? or is there more under the hood than meets the eye?
I am not talking about the shared code library because I realize it is specific to Xamarin.Forms but rather (for example) if I am to compare a Xamarin.Droid project to an android codebase of a Xamarin.Forms solution, will I find any considerable differences? Will I find any differences. Same goes for IoS & Windows...
Just to provide context; I am interested in utilizing some tools which were originally designed for Xamarin.android however my projects are Xamarin.forms solutions and it would be cool to know in advance if I am running into a rathole.
Thanks in advance you fine people.
Xamarin Forms, in the end, is a wrapper over the native API's so if you have something in Xamarin Forms you can of course port it to Xamarin Android, iOS or Windows.
Is Xamarin.Forms considered a simple sum of Xamarin.Android and Xamarin.IoS with a shared code library wrapper? or is there more under the hood than meets the eye?
At its simplest, Xamarin.Forms is a mobile application framework for building user interfaces. The definition from Xamarin's website is:
Xamarin.Forms is a cross-platform UI toolkit that allows developers to easily create native user interface layouts that can be shared across Android, iOS, and Windows Phone.
But don't simply focus on the term "UI" in that definition and think only on-screen controls. Instead, focus on the word "toolkit" as Xamarin. Forms offer so much more in addition to user interface controls that work across platforms.
Xamarin.Forms will emit a 100% native iOS, Android or UWP app – in fact the starting point of any Xamarin.Forms app is within one of those platform projects. However, that's as far as the platform-specific code needs to go. The rest of the code can all be written in one of the layers that are shared amongst all the applications.
if I am to compare a Xamarin.Droid project to an android codebase of a Xamarin.Forms solution, will I find any considerable differences? Will I find any differences. Same goes for IoS & Windows...
Just Basic API differences, which are different between forms and native
You shoud see Xamarin.Forms as the abstraction of the UI over the actual platform. Xamarin.Forms (XF) renders the UI in native platforms controls, but they are created using XF XAML.
Coding against XF is like coding for a different platform with a different set of tools, at the UI level!
You can, if needed go deep in platform specific details if needs be via interface implementation and injection.
Though this is a duplicate question, it would be really great if someone can help me in integrating a DICOM image viewer in my iOS application. Basically we are building a health application, where we have a requirement to showcase .DCM images. Any solutions ?
I'd tried with this and this too. But no luck :(
Imebra (c++) can be compiled for OS-X and iOS.
It comes with few objective-c helpers that convert images to UIImage or NSImage and std::string objects to/from NSString.
The documentation contains a section dedicated to building the library for Apple OSes.
Disclosure: I'm the author of Imebra
I am currently the primary maintainer of fo-dicom, which is a C# based cross-platform DICOM toolkit, available on .NET Framework, but also on Xamarin iOS, Xamarin Android as well as other platforms.
If you are considering developing in C#, fo-dicom might be a sufficient alternative.
It is really not practical to write a Xamarin.Forms application without a UI previewer. All platforms offer a design preview option, especially if the code needs to be compiled. As far as I know, currently Xamarin only released a previewer for Xamarin Studio for Mac in its alpha channel, which we can't even use in Visual Studio. Why is it that Xamarin still does not provide a previewer? We should not be forced to use a third party tool for this process. (And even the third party tools are in their beta releases.)
Shouldn't there be at least a roadmap or a planned date announced since it is such a fundamental part of the product? It would be nice if someone from Xamarin would answer.
Using the latest version of Xamarin you can use the following steps:
Use the View > Other Windows > Xamarin.Forms Previewer menu in Visual Studio to open the preview window.
The Xamarin.Forms Previewer is there on Windows (it has been for a few years), but it now contains several improvements in Visual Studio 2019, many focused on making it more reliable.
To show the Previewer, click the design buttons on the bottom right of the .xaml file pane, like chucky mentioned. It's no longer under View > Other Windows, instead now using the same split pane tabbed UI used by the UWP/WPF designers.
See here for more on how to use the Previewer:
https://learn.microsoft.com/en-us/xamarin/xamarin-forms/xaml/xaml-previewer/?tabs=vswin&pivots=windows
I use VS2012 and everything is from stable channel only. Also MVVMCross is up to date.
I thought Xamarin already released official support for async/await in PCL?
But I still can't add System.Threading.Tasks in the Core PCL project.
I read that somewhere we can change it Profile78 to make it work naively.
But latest mvvmcross still using profile104, there must be a reason for that?
My question is how can I get async/await working naively or non-natively on profile 104?
Thanks in advanced!
I thought Xamarin already released official support for async/await in PCL?
Xamarin have told me that they have not officially announced any PCL support (although their release notes show they have shipped bits).
MvvmCross ships using Profile104 because MvvmCross supports WP7 - but that doesn't mean your apps need to use Profile104 - you can use the profile you want to use (as long as it can consume 104)
Until Xamarin officially release their PCL support and more information about it, then I think the answer to this question remains at TPL on PCL of mvvmcross and Async/Await in portable class library targeting Windows Store, iOS and Droid