Library 2.0 Add Ons Organization

Keith Alfaro edited this page Mar 5, 2018 · 1 revision

Defining Custom Package Organization (Dynamo 2.0)

Achieving a desired layout for your package depends on the types of nodes you will be including in your package. Node Model derived nodes, ZeroTouch nodes, and Custom nodes all have a slightly different process for defining the categorization. You can mix and match these node types within the same package, but it will require a combination of the strategies outlined below.


NodeModel libraries are organized based on the class structure by default.

namespace SampleLibraryUI.Examples
// Class Attribute
public class MyNewNodeModel : NodeModel

// or

// Constructor
public ButtonCustomNodeModel()
    this.Name = "MyNodeModel";

Node will be located in Add-ons under:


You can also override the category by using the NodeCategory attribute on the class or in the constructor as shown below.

// Class Attribute

// or

// Constructor
public ButtonCustomNodeModel()
    this.Category = "NewSampleLibraryUI.Examples";

The node will now be located in Add-ons under:



ZeroTouch libraries are also organized based on the class structure by default.

namespace MyZTLibrary
public class Utilities
    public double doubleValue(double num)
        return num * 2;

Node will be located in Add-ons under:


You can also override the class structure location by using a Dynamo Customization XML file.

  • The XML file must be named accordingly and be included in the extra folder of the package
    • PackageName_DynamoCustomization.xml
<?xml version="1.0"?>
        <!--Remap Namespaces-->
        <namespace name="Autodesk.Dynamo.MeshToolkit">
        <namespace name="Autodesk.Dynamo.MeshToolkit.Display">
        <!--Remap Class Names-->
        <class name="Autodesk.Dynamo.MeshToolkit.Display.MeshDisplay" shortname="MeshDisplay"/>
        <class name="Autodesk.Dynamo.MeshToolkit.Mesh" shortname="Mesh"/>


Custom nodes are organized based on the specified Category Name during the nodes creation (using the new Custom Node dialog box).

Using dot-notation in node Names or Categories will result in additional nested sub-categories. The . will work as a delimiter to determine the additional hierarchy. This is new behavior in the library for Dynamo 2.0.


The Category Name can later be updated in the .dyf file (XML or JSON)

  "Uuid": "85066088-1616-40b1-96e1-c33e685c6948",
  "IsCustomNode": true,
  "Category": "MyCustomNodes.Utilities.Actions",
  "Description": "This is an example custom nodes.",
  "Name": "doubleValue",
  "ElementResolver": {
    "ResolutionMap": {}
<Workspace Version="" X="100" Y="100" zoom="1.0000000" Description="This is an example custom nodes." Category="MyCustomNodes.Utilities.Actions" Name="doubleValue" ID="85066088-1616-40b1-96e1-c33e685c6948">
Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.