Namespace Xbim.Common
Classes
CrossSchemaAttributeAttribute
DefinedTypeAttribute
EntityAttributeAttribute
ExpressTypeAttribute
FlagSetter
IndexedProperty
Indicates that this property plays a role in some inverse relation
InverseProperty
ModelHelper
PersistEntity
PersistEntityExtensions
Extension methods for the IPersist interface.
PlaceboTransaction
A class of transaction that has no impact and does nothing used when another transaction is normally running
XbimAssemblyInfo
This class can be useful to understand exact version of the xbim assemblies used.
XbimInstanceHandleMap
A class for holding mappings between instances in one model and instances in another model
XbimLogging
A helper class to centrally manage logging
XbimModelFactors
Structs
XbimInstanceHandle
A lightweight structure for obtaining a handle to an Ifc Instance, the instance is not loaded into memory unless the GetInstance function is called IfcInstanceHandle are specific to the model they were generated from
Interfaces
IContainsEntityReferences
IContainsIndexedReferences
IEntityCache
Some implementations of IModel might use optimized data handling where entity data is loaded on the fly from database, file or other source. For some scenarios it is usefull to keep entities alive in the cache so they don't get disposed and every entity only has one instance.
IEntityCollection
IEntityFactory
IExpressBinaryType
IExpressBooleanType
IExpressComplexType
IExpressEnumerable
IExpressHeaderType
IExpressIntegerType
IExpressLogicalType
IExpressNumberType
IExpressRealType
IExpressSelectType
IExpressStringType
IExpressValueType
IInstantiableEntity
IInverseCache
Inverse relations are one of very important concepts in EXPRESS modeling which allows to mimic safe bi-directional relations between two objects. But because EXPRESS model is always flat list of entities some queries using inverse properties for navigation in model cause exponential cost if the data search. That is obviously not optimal. Inverse cache should help especially in cases where the IModel implementation doesn't have any secondary indexing mechanism for inverse relations. It can usually only be used outside of transaction. Starting transaction when caching is on might raise an exception. You should always keep inverse cache object inside of using statement.
IItemSet
IItemSet<T>
IModel
IModelFactors
IOptionalItemSet
IOptionalItemSet<T>
IPersist
IPersistEntity
IPropertyValue
IReadOnlyEntityCollection
ITransaction
Enums
ChangeType
EntityAttributeState
The scope of the entity attribute
EntityAttributeType
ProjectUnits
Could do with Imperial :-)