This project deliberately uses "C++/CLI" instead of the more common "C#". This makes sense in several scenarios.
- 📚 Educational Objective: This project serves as a visual aid on how to work with cross-language interoperability in the .NET and Revit ecosystem.
Create file .addin in the directory X:\Users\%USER%\AppData\Roaming\Autodesk\Revit\Addins\20XX\
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<RevitAddIns>
<AddIn Type="Application">
<Name>VPlug</Name>
<Assembly>"%your_path%\VPlug.dll"</Assembly>
<AddInId>{75B71A2F-2ACD-48CE-8518-FF869D3A8440}</AddInId>
<FullClassName>VPlug.Main</FullClassName>
<VendorId>vasyusha</VendorId>
<VendorDescription>https://github.com/vasyusha/VPlug-Revit</VendorDescription>
</AddIn>
</RevitAddIns>VPlug/
├───Configuration/ # configuration file examples
│ └───Parameter_Checks/ # checking parameters are filled
├───Executable/ # executable files
│ ├───Commands/ # plugin function initialization files
│ ├───Config/ # configuration processing
│ │ └───json/ # processing json
│ ├───Export/ # export processing
│ │ └───html/ # export html
│ ├───Revit/ # wrappers, helper classes, functions for RevitAPI
│ │ ├───Elements/ # Revit element wrappers
│ │ ├───Filters/ # filtering, searching, customization
│ │ └───Services/ # logic of elements and work
│ └───UI/ # visual representation
│ ├───VPControls/ # Controls
│ └───VPForms/ # Forms
└───Headlines/ # header files
├───Commands/ # plugin function initialization files
├───Config/ # configuration processing
│ └───json/ # processing json
├───Export/ # export processing
│ └───html/ # export html
├───Revit/ # wrappers, helper classes, functions for RevitAPI
│ ├───Elements/ # Revit element wrappers
│ ├───Filters/ # filtering, searching, customization
│ └───Services/ # logic of elements and work
└───UI/ # visual representation
├───VPControls/ # Controls
└───VPForms/ # Forms
| Панель | Действие | Что делает | Как использовать | Документация |
|---|---|---|---|---|
| Проверка | Проверить/Заполнение параметров | Очевидно | (В работе) | (В работе) |