How autodesk/revit-ifc works
Project type and purpose
• This is a .NET Visual Studio solution (Revit.IFC.sln) that implements IFC import/export functionality as Revit add-ins and a complementary desktop tool.
• Main use cases:
• Export Revit models to IFC file format (via Revit.IFC.Export and IFCExporterUIOverride).
• Import/Link IFC files into Revit (via Revit.IFC.Import).
• Provide a standalone WPF application (RevitIFCTools) for generating and inspecting IFC property‐set definitions.
• Package everything into an installer (Install/RevitIFCSetupWix) and produce add-in bundles.
File structure
• Top-level projects under Source:
• IFCExporterUIOverride (WPF UI override for export settings)
• Revit.IFC.Common (shared enums, extensions, utilities)
• Revit.IFC.Export (core export engine, property‐set calculators, toolkit, caches)
• Revit.IFC.Import.Core & Revit.IFC.Import (import engine, geometry processing, data classes)
• RevitIFCTools (standalone WPF tool for Pset definitions and schema operations)
• Installer: WiX project and add-in bundle files under Install
• ThirdParty: external dependencies (e.g., ANTLR, ICSharpCode)
• VSProps: shared build props/targets for Revit SDK integration
README for additional insights
• Confirms two principal flows: Exporting (ExportIFC in Exporter.cs) and Importing (ImportIFC in Importer.cs).
• Describes build, debugging steps, and where DLLs get deployed in Revit’s add-in folder.
• Notes dependencies (Revit DLLs, NuGet packages, ANTLR 4).
Elements
• from Revit Host to Add-in modules
• between modules to show function calls or data access
• to/from file system components for IFC schema and output files
• another for tooling (RevitIFCTools)