Change assembly name for v2 to avoid host conflicts - #5
Merged
Conversation
KodrAus
approved these changes
Sep 1, 2026
Member
Author
|
I'll send this through and update the mail apps (the only ones currently depending on it) - may be a bit more churn today while I figure this out. |
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
2 participants
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.
With this change, hopefully, apps and hosts that disagree on which Seq.Syntax version to load can continue working:
In the long run, I hope that we can switch .NET plug-in apps to use an EXE-based model that skips any reliance on
seqcli(possible, but not trivial). In the meantime, keeping Seq.Syntax versions under the same major semver number (and assembly name) binary-compatible should avoid most problems.