Announcement

Collapse
No announcement yet.

Pre-approved unsigned addins: issues with ZoomToAwesom(er)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Pre-approved unsigned addins: issues with ZoomToAwesom(er)

    When dealing with unsigned addins, normally I can copy the GUID in the <ClientId> node in the addin manifest, then create (using PowerShell) a DWord value of that name in HKCU\Software\Autodesk\Revit\Autodesk Revit 2017\CodeSigning, with a value of 1.
    But with ZoomToAwesomer (the recently updated ZoomToAwesome for Revit 2016 & 2017) that doesn't work. There are two components of the Manifest, a Command and a Application, and I have pushed both GUIDs to the registry, but on launch I still get the user interaction. And, when I review the registry, it seems as if nothing has changed between what I pushed in advance and what Revit did when I chose Always Load manually. Initially I thought perhaps I had something odd going on with encoding, but both the manifest and my file where I am referencing the GUIDs are UTF-8. So then I tried cutting and pasting the names direct from a working registry, which is the approach I was using before I discovered that the GUIDs are in the manifest. Still, no joy. Now I wonder, is there something else that needs to be done, besides the Words in CodeSigning? That doesn't make a lot of sense, since other addins have worked fine with just that intervention. But it also doesn't make sense (to me at least) that just this one app would be misbehaving.

    Thoughts?
    Pragmatic Praxis
Loading...
Working...
X