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

[jeremytammik]

dear roman, @Nice3point , i suggest you do not use the term Revit 2026. just say future release, or preview release, or something until the final product has been publicly released. using that term might be on the limits of violating the NDA. by the way, i had a request today from the development team for an autodesk internal version of RevitLookup for the preview release. would you be capable and willing to provide that to them? thank you!

[Nice3point]

@jeremytammik already sent the pre-release builds to Weiwei's email, hope he got it. I don't think I mentioned 26 anything in this PR, except for Milestone, no problem I will remove it

[jeremytammik]

wow, great, i'm sure that made him happy. oh, i just saw the words in the github email notification. i don't know where they came from. thank you for taking such good care!

[Nice3point]

most likely you have received a notification that the “Code quality” Pipeline has failed, its about JetBrains service, not Revit. For now, it will always fail with an error because the license has expired. We have requested a renewal from jetBrains

[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.