RevitTemplate Namespace

This is the ExternalCommand which gets executed from the ExternalApplication. In a WPF context, this can be lean, as it just needs to show the WPF. Without a UI, this could contain the main order of operations for executing the business logic.

This is an example of of wrapping a method with an ExternalEventHandler using a string argument. Any type of argument can be passed to the RevitEventWrapper, and therefore be used in the execution of a method which has to take place within a "Valid Revit API Context".

This is an example of of wrapping a method with an ExternalEventHandler using an instance of WPF as an argument. Any type of argument can be passed to the RevitEventWrapper, and therefore be used in the execution of a method which has to take place within a "Valid Revit API Context". This specific pattern can be useful for smaller applications, where it is convenient to access the WPF properties directly, but can become cumbersome in larger application architectures. At that point, it is suggested to use more "low-level" wrapping, as with the string-argument-wrapped method above.

Class for creating Argument (Wrapped) External Events

Interaction logic for UI.xaml