- Digitalpersona u.are.u sdk for windows driver#
- Digitalpersona u.are.u sdk for windows pro#
- Digitalpersona u.are.u sdk for windows code#
In the end, I give DP 4 stars and Griaule sdk 3 stars.
Digitalpersona u.are.u sdk for windows driver#
Maybe also put up a ClickOnce site for point and click deploy of sdk and driver updates.
Again, they need to get over themselfs and rollout a single DLL with 2-4 public methods and call it a day.
Net libraries included, but requires 4 references to different dlls to get enroll and verify working. This may even push people over to Griaule and MS reader.Ħ). Seems like a money grab that only will put off new developers. I don’t get this idea of charging for an sdk when you have to buy there hardware anyway. Net support seems cleaner then Griaule’s.Ĥ) Performance is acceptable, but feels a tad slower then Griaule sdk and MS Reader.ĥ) The have another sdk they charge 600 bucks for. I mean 90% of time, you want a finger press event and a Verify function and that is it.
Digitalpersona u.are.u sdk for windows code#
The event model seems strange also.Ģ) Could be abstracted more and remove a lot of un-needed code and namespaces. Almost like they are ported from java or something.Net naming standards not followed. In my mind, this is a big deployment winner without needing another setup step for customer.Ĩ) Can serialize the fingerprint sample and send it over the wire for server verify.ġ). It has “weight” and stays on the desk better then MS reader (which would need to be taped down in a production environment).ħ) Windows Vista recognized and installed the driver on plug-in without the CD. The finger reader just feels good and built well. This is most annoying thing and I was prompted to look elsewhere for this reason.Ĥ) Does not require any client license (just the hardware).Ħ) Hardware good. Net projects and does not allow console or server side verify.ĥ) Does not support other hardware so does not work with Microsoft reader (which is strange because the MS internals use DP hardware)Ħ) Grtools tray app installed and wants to take over your machine. This complicates deployment and support greatly.Ĥ) API tied to windows UI controls. Requires each client have a txt license tied to machine id. Both products seem to have “over-built” these SDKs and seem to think the focus of your app is there SDK, which is not the case.ġ) Works with many readers (including MS Reader)ģ) Licensing.
Both products worked for me and both have pros and cons in the sdks. In about a day, I fixed my app to work with new sdk.
Digitalpersona u.are.u sdk for windows pro#
I then purchased a digitalPersona U.are.U 4500 reader and downloaded their free SDK to test it out. The U.are.U 4500 Reader can be purchased for use with DigitalPersona Pro Workstation, DigitalPersona Pro Kiosk, DigitalPersona Online, DigitalPersona Personal or any of the DigitalPersona SDK packages. However, after looking at deployment issue, I found this was not going to work well for me or my customers. I originally developed my app with the Microsoft Reader and the Griaule SDK. Have switched my TimeExpress biometrics app to using DigitalPersona and am pretty happy so far.
0 kommentar(er)
