The team are working on moving EMDK for Xamarin to Nuget as a priority.
As a workaround, Visual Studio will still offer you the component store if your project has an existing component. You can manually add the component by editing the .csproj file:
- Copy the samples-emdkforxamarin-2_5/BarcodeSample1/Components at BarcodeSample1 · Zebra/samples-emdkforxamarin-2_5 · GitHub folder to the equivalent place in your project.
- Add this reference to Symbol.XamarinEMDK: samples-emdkforxamarin-2_5/BarcodeSample1.csproj at BarcodeSample1 · Zebra/samples-emdkforxamarin-2_5 · GitHub
- Add this item group for Xamarin components: samples-emdkforxamarin-2_5/BarcodeSample1.csproj at BarcodeSample1 · Zebra/samples-emdkforxamarin-2_5 · GitHub
Not ideal I know but it will work for a new project with the latest version of VS2017. Alternatively you can just use samples-emdkforxamarin-2_5/BarcodeSample1/BarcodeSample1 at BarcodeSample1 · Zebra/samples-emdkforxamarin-2_5 · GitHub or one of our other sample apps as the starting point for your application.
Hope that helps.
Thanks, that's what I'd ended up doing before I saw your reply. However, I am still unable to scan, however.
I downloaded the sample from:
and was able to get it to run, but it does not respond to trigger presses and the UI keeps refreshing. I also tried creating a new project (blank Android) and copied the code from:
into it and got the same behaviour. I'm in windows 10, running Visual Studio 2017. I'm using the MC3300, which has Android 7.1.2. I've tried the EMDK For Xamarin 2.5 component, as well as the EMDK For Xamarin 188.8.131.52 and 184.108.40.206 components.
I see that the MC330 is listed as tested with the EMDK 2.7 on this page:
but none of the samples at:
list the MC3300. Also, all the Sample download links and zips point to version 2.5 in GitHub.
When I run any of the sample/tutorial apps, what will happen is that the UI will continuously refresh, and most of the time the trigger will not activate the scanner. Occasionally it does, and the device beeps, but the scanner_Data callback is never hit. I've tried taking out all UI update code, but it still rarely triggers the laser and never hits the data callback.
I thought maybe it was a hardware issue, but the DWDemo app that came pre-installed works correctly. If I can use Intents sent from DataWedge in Xamarin C#, I'll do it that way if I have to. I don't know if there's some detail I'm missing with the EMDK, but I've tried several versions of the barcode sample and the barcode tutorial and have not yet been successful.
Ah, so that could well be the issue, that you need EMDK for Xamarin 2.7 in order to have it working / supported on the MC33. I don't even see 2.7 listed at the official component store: EMDK For Xamarin / Components / Xamarin so I do not think it is out yet. The documentation you linked to must be some draft version which is not yet meant to be public.
I do not have access to an MC3300 but I tested on my TC51 just to be sure the problem wasn't related to using the latest version of VS2017 and my TC51 worked fine which indicates to me you just need to have EMDK 2.7.
I'll try and find out when 2.7 is due for release.
For DataWedge, this may well be a more reliable route for you right now. There is not an official sample for this but I have an unofficial sample on my github (GitHub - darryncampbell/DataWedge-Intent-Example-3 ) as well as a tutorial on my personal site (Tutorial: Scan with Datawedge Intent output on Zebra devices (with Xamarin) – DARRYN CAMPBELL BLOG ), again, unofficial.