03-09-2012 10:34 AM
Just wanted to get a sense of how well everyone understands the concept of and installation steps of using debug tokens.
Do you feel the documentation clearly explains how to ...
03-09-2012 02:16 PM
I recently revisited the doc in order to implement a multi-vendor app building workflow and everything was clear. It's great to be able to leave the signing part to the very end, when submitting the app.
03-09-2012 04:46 PM
I certainly understand them now. That doesn't stop me from having a snippet area for the process of creating them. Having to use 0x notation for the pins is annoying. Having two passwords to access the signing information is similar. Finally, having all the signing information tied to a specific machine is stupid (a bit off topic).
The whole signing process needs to be simplified. I understand the need to identify publishers but the process is painful.
03-10-2012 07:24 AM
Once I followed all the steps properly it was fine. That said the whole process seems a bit long if it could be simiplified I think it would be less error prone.
03-11-2012 10:47 AM - edited 03-11-2012 10:51 AM
It give you no idea, i ended signing everything.
But the really problem comes with the way you get to the dicumentation not with the tokens documentation itself.
03-12-2012 10:15 AM
Thanks everyone who has provided feedback so far.
arqiz - do you mean the discovery of debug token documentation needs to improve? Let me clarify - how did you know you needed / wanted to use a debug token, and where did you first look to find that information?