Repository navigation
[Build] Update Revit Injector to the latest patch versions - #67
Merged
Merged
Conversation
Nice3point
added
bug 🐛
Nice3point
marked this pull request as ready for review
November 2, 2026 11:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of the Pull Request
What is this about:
A
RevitApiUiBenchmarkon Revit 2025 loads one copy of a runtime assembly the benchmark project ships a later package of.Description:
What changed
.11to.12for every Revit version. The load context of the UI application binds every reference of an assembly name to one assembly, and a later package copy wins over the runtime copy.2027.0.3..3.How verified
Debug.R25andDebug.R27succeed against Revit Injector2027.0.12and2025.1.12.Quality Checklist