Component Isolation from Revit

[Nice3point]

Summary of the Pull Request

What is this about:

Update the Solution structure to provide more flexible development and isolate projects from each other.

A new ability to create plugins based on LookupEngine #278

Description:

• Net 9 support
• Solution .slnx format support
• Isolated LookupEngine
• Isolated UI framework
• Engine tests and benchmarks
• Full independence of critical components from Revit
• Revit integration

Quality Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• All exceptions are caught in async void blocks
• Some commons utils moved to Nuget

[Nice3point]

@jeremytammik Jeremy if you has some time, could you please verify a Card description for tools ?
https://github.com/jeremytammik/RevitLookup/blob/dev_environment/source/RevitLookup.UI.Playground/Mockups/ViewModels/Dashboard/MockDashboardViewModel.cs#L42

It will be displaying on the dashboard:

[jeremytammik]

you mean run it and Explore and analyze the model's visual representation? ... how should that be done?

[jeremytammik]

oh i think i understand what you mean now. you mean proof read the descriptions that you have written for each card? sure, i will do that immediately.

[jeremytammik]

done, PR #306 submitted.

[Nice3point]

Oh thanks, but Schemata uses in the Revit api? i guess no) https://www.revitapidocs.com/2016/9817e7db-8367-ea4e-1769-0488f3faa37f.htm

[jeremytammik]

nope. it is the officially correct plural of schema, though, afaik. but feel free to use schemas if you prefer. nobody will complain. i will feel the pain, but that is just poor little me.

[Nice3point]

so both are possible)

https://english.stackexchange.com/questions/77764/plural-form-of-schema

The Greek schemata is mostly found in academic writing (e.g. experimental schemata), whereas the anglicized schemas is used freely in both technical and more general discourse (e.g. database access schemas).

[Nice3point]

@SergeyNefyodov History added: https://github.com/jeremytammik/RevitLookup/blob/dev_environment/source/RevitLookup.Abstractions/Services/Decomposition/IDecompositionService.cs#L8

So you can rework FamilySizeTableEditDialog and other dialogs. Now we have a navigation context. Currently FamilySizeTable removed from the new codebase, because it has a lot of Revit dependencies, we need abstractions, but original files store in the RevitLookup.Obsolete project.

New menu registration format:
https://github.com/jeremytammik/RevitLookup/blob/dev_environment/source/RevitLookup/Core/Decomposition/Descriptors/BoundingBoxXyzDescriptor.cs#L139

var decompositionService = serviceProvider.GetRequiredService<IDecompositionService>();
decompositionService.DecompositionStackHistory //Find parent context to pass to your method

No documentation for now, will be later.

[jeremytammik]

I guess I will not mention this in public yet, to avoid mentioning the dreaded 2026 word before the corresponding official product release...

[Nice3point]

This is a version of RevitLookup, not a future release of Revit, these are different products with own versioning system
And I guess yes, it's okay to not post the preview versions on the blog