2011-10-17 04:00 AM - last edited on 2023-08-02 09:11 PM by Doreena Deng
2011-10-17 04:51 AM
2011-10-17 05:33 AM
Karl wrote:I did this, Karl.
When I got my Developer ID, it was a four character text string. This string is not acceptable as the MDID in the grc file - it had to be converted to a numeric hex value of the form 0xAABBCCDD where AA is the hex encoding for the first character of the dev id, etc.
Karl wrote:And also did this.
(You also have to generate a unique add-on ID from your dev ID.)
2011-10-17 05:09 PM
2011-10-18 03:35 PM
fredfreitas wrote:It's most likely to be a problem with the add-on's resources - either the compiler isn't generating the right information or the resources aren't linked into the add-on.
I have a Developer ID, I already got the "AddOnAdmin" output numbers and put them in grc file (3D_TestFix.grc). I am trying to load that sample, "3D_Test", but even after compiling it and copy the "3D_Test.bundle" from the Debug folder to the Add-Ons folder, this thing is still red at "Add-On Manager" (Add-On info: This add-on cannot be validated. Please contact the distributor).
2011-10-21 10:57 PM