ricaun-io / revitaddin.da.tester

RevitAddin Tester for Design Automation (Forge)

RevitAddin.DA.Tester

Revit Addin project to run in Design Automation with some simple file input.json and output.json.

Input / Output

├── ...
├── input.json
├── output.json
└── ...

InputModel.cs

public class InputModel
{
    public string Text { get; set; }
    public int Sleep { get; set; }
}

OutputModel.cs

public class OutputModel
{
    public string VersionName { get; set; }
    public string VersionBuild { get; set; }
    public DateTime TimeStart { get; set; } = DateTime.UtcNow;
    public string Text { get; set; }
}

Installation

• Download bundle version RevitAddin.DA.Tester.bundle.zip
• Download and install RevitAddin.DA.Tester.exe

License

This project is licensed under the MIT Licence.

---

Do you like this project? Please star this project on GitHub!

revitaddin.da.tester's Issues

Design Automation for Revit ignores `PackageContents.xml` configuration.

By default Design Automation for Revit selects the first ComponentEntry in the PackageContents.xml ignoring the version defined in the RuntimeRequirements.

In the example below, the version 2021 of the .addin is loaded by default even if is selected the engine for Revit 2025.

<?xml version="1.0" encoding="utf-8"?>
<ApplicationPackage SchemaVersion="1.0" AutodeskProduct="Revit" Name="RevitAddin.DA.Tester" AppVersion="1.3.0" ProductType="Application" ProductCode="7c324916-9f8d-43b0-b226-da67d2504393">
  <Components Description="Revit 2021">
    <RuntimeRequirements OS="Win64" Platform="Revit" SeriesMin="R2021" SeriesMax="R2021" />
    <ComponentEntry AppName="RevitAddin.DA.Tester" ModuleName=".\Contents\RevitAddin.DA.Tester\1.3.0-beta.1\2021\RevitAddin.DA.Tester.addin" />
  </Components>
  <Components Description="Revit 2025">
    <RuntimeRequirements OS="Win64" Platform="Revit" SeriesMin="R2025" SeriesMax="R2025" />
    <ComponentEntry AppName="RevitAddin.DA.Tester" ModuleName=".\Contents\RevitAddin.DA.Tester\1.3.0-beta.1\2025\RevitAddin.DA.Tester.addin" />
  </Components>
</ApplicationPackage>

A reusable solution would be to first search for the right version of the engine in the bundle. And if the version does not exist in the PackageContents.xml, select the first one like in the current version of the DA4R Revit 2025 (RVTDA 04-04-2024).