XbimEssentials
XbimEssentials copied to clipboard
xBimTeam
A .NET library to work with data in the IFC format. This is the core component of the Xbim Toolkit
According to the [official documentation](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/lexical/IfcBoxAlignment.htm), IfcBoxAlignment can take in only a selected values, in this case, an Enum representation is quite appropriate. But in xBIM IfcBoxAlignment takes in a string....
Here's the code: static void Main(string[] args) { var projectName = "Virtual Element Test"; var fileName = @"VEElement.ifc"; var credentials = new XbimEditorCredentials(); using (var model = IfcStore.Create(credentials, XbimSchemaVersion.Ifc4x1, XbimStoreType.InMemoryModel))...
Every IFC version has its own namespace and often different schema mapping rules to apply. We need to investigate the latest documentation and implement XML serialization and deserialization support.
There is new [C# language feature](https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/tutorials/nullable-reference-types) which we can use for optional IFC attributes. This will help developers to write safer code.
Model providers should not be set up statically. They actually need to be re-designed to be more sensible and useful.
Build pipeline needs to be updated. - It need to be simplified. It manipulates projects to create NuGet packages, but this is unnecessary. NuGet will do this automatically. - Xbim.Essentials...
New memory operations are supported in .NET Standard. This was implemented back in 2020, but was reverted back in SHA 8555eb3be90f9fb06711e6347c546a67ce9a36a7 It should be re-introduced with compiler flag for NETSTANDARD...
The current documentation was generated with Sandcastle. We should move to use a modern tool like Docfx and make documentation generation part of the build pipeline.
https://stackoverflow.com/a/29414133 https://learn.microsoft.com/nuget/create-packages/symbol-packages-snupkg
