M-V-VM Pattern for Revit, part 3

In the previous articles of this three-part series, we explored the foundational principles of the Model-View-ViewModel pattern for Revit add-in development. We began constructing a simple add-in to demonstrate these concepts, such as how to display Model data to the…

M-V-VM Pattern for Revit, part 2

As a Revit API developer, the Model-View-ViewModel pattern is essential to learn if you’re looking to build more complex and scalable add-ins. In the first article of this three-part series, I have presented this pattern’s main principles and key points.…

M-V-VM Pattern for Revit, part 1

Transitioning from Dynamo scripting to Autodesk® Revit Add-in development introduced me to a higher level of software complexity. It required me to consider various aspects, including database connections, user interface creation, authentication checks, and the organization of multiple C# and…

Towards element-specific coordinate systems

One of the challenges I encountered with the Revit API was about defining the spatial positions of a model’s elements in relation to each other. I had to consider this issue when automating the control of openings within a wall,…

Transforming solids

When using the Revit API, we often perform tasks involving multiple geometries. For instance, we might compare their positions or identify their intersections. However, it’s important to note that even if these geometries appear close in the Revit 3D space,…