I would like to have some documentation inside Xamarin Studio. It would be helpful to see the documentation of the .NET framework methods or the documentation of the iOS methods.
Is there any way to enable this? Or some way to hack it in there myself?
Help - API Documentation will open MonoDoc.
MonoDoc will give you documentation on the .NET Base Class Library.
On the Mac it will also give you the option to merge the iOS documentation from Apple.
Related
This sounds like a very simple question, but please don't have a go at me. I have tried searching. perhaps i'm just using the wrong terminology.
I'm not new to visual studio, i've been using it ever since version 6... but i am relatively new to .net.
I have written apps which used nuget libraries. this is a piece of cake. but now I want to use this library:
https://github.com/anotherlab/UsbSerialForAndroid
how on earth do i add this? There's no nuget?
Thanks
Andrew
I've read the open source parse docs, and looked at the parse c# sdk. I also looked at back4app but their example is way out of date. I can't tell if I'm supposed to take the c# code from the official parse sdk and try to put it in Unity or am I supposed to build a dll first? There's not a lot of information that I can find.
The latest official release for this SDK was in 2016, as you can see here: https://github.com/parse-community/Parse-SDK-dotNET/releases/tag/1.7.0
There's a fork of Parse SDK that usually works fine, have you already seen it?
Here it is: https://github.com/fayezsalka/Parse-for-Unity-2018
I am working on a Xamarin.Forms project.
I have to create an ID card from the details provided, in a certain format and print the same.
How can this be done?
Has anyone tried something like this?
Disclaimer: I have NOT tried the following solution myself.
There is no out-of-the-box support in Xamarin.Forms for printing PDF.
The best practice, in terms of safety and native-performance, would be to use Dependency Injection by defining an interface in the portable (CPL or .NET Standard) project and implementing the actual printing code in the native projects you wish to target.
The following are the APIs for their respective platforms:
For Android: https://developer.xamarin.com/api/type/Android.Print.Pdf.PrintedPdfDocument/
For iOS: https://developer.xamarin.com/api/type/MonoTouch.UIKit.UIPrintInteractionController/
More of the same:
https://www.syncfusion.com/kb/8767/how-to-print-pdf-documents-in-xamarin-forms-platform
Hope it helps. Cheers!
Hello I would like to make a project for Vuzix M300 Smart Glasses. In order to do so I need to get some information about my device in my PCL.
I found some Xamarin Plugins which did not really solve my problem.
So is there a way to get information about the current device like: vuzix M300 in my Visual Studio?
After all I found the answer by myself.
I used the Xamarin Forms Dependency Services to get the information into the pcl.
If you try to call the Plugin within the pcl you will get an exception.
I have tricky question about SignaturePad updated to Xamarin Forms 2.0, link to GitHub:
https://github.com/mrbelk/acr-xamarin-forms
I did manage to download repo and build it, however I have no idea how to produce proper DLLs that I could use in my project?
The main issue is that SignaturePadView is treated as Xamarin Forms View class instead of Android View, so there is different constructors, methods, etc.
Does smb know how to build these projects to produce proper dlls that iOS/Android solution will treat SignaturePadView as Android View and iOS UIView respectively?
Don't use acr.* any more if you want to save yourself some pain. I had to pull their camera implementation out of one of my apps due to no support for forms 2.0+.
Replace acr with supported NuGets like Plugin.Media and the others found here. For this particular issue no one has created a non-deprecated NuGet so there is this plugin as an option.
Apparently, it happens that we have actually used SignaturePad from https://components.xamarin.com/view/signature-pad but via acr.* nuget package.
What I found in my quick research that both acr.xamforms.SignaturePad and SignaturePad it self were in acr nuget package, and actually we were using components from SignaturePad, luckily. So I did remove this nuget from sln to get rid of acr.* components and add SignaturePad from xamarin components by hand.
Now we are able to use Xamarin Forms 2.0 without any problems.
Cheers,
G