Compile Publisher, Subscriber, and tests against one shared engine#18
Merged
Conversation
masarray
marked this pull request as ready for review
July 12, 2026 01:37
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Purpose
Remove the largest remaining architecture risk identified in the repository audit: Publisher, Subscriber, and Tests previously compiled separate copies of the IEC 61850 source.
Changes
src/ARSVIN.Engine/ARSVIN.Engine.csprojas the single shared protocol assembly.ARSVIN.Enginefrom Publisher and remove Publisher's implicit duplicate engine compilation.InternalsVisibleTodeclarations for Publisher, Subscriber, and Tests.ARSVIN.sln.Why
The old structure could compile the same protocol source into multiple assemblies with different compiler context, dependencies, and internal visibility. Tests also did not execute the exact production assembly shipped with the applications. The new structure creates one source of compiled protocol behavior and makes test coverage represent the shipped engine.
Validation completed
ARSVIN.Engine: success.ARSVIN.Engine: success.Validated release workflow artifact:
ARSVIN-0.0.0-pr.31-windows-x64sha256:960e6a06dd48f67325a0e07c94df18a8818c1379a55c3fa047a2ce1518d0c2f3Follow-up
After this transition proves stable, a later mechanical PR can move the physical engine source directory from
src/ARSVIN/Engineintosrc/ARSVIN.Enginewithout changing runtime behavior. Broader protocol tests should then raise the full-engine baseline progressively.