Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopt assembly versioning scheme 'major.minor.0.0' #554

Merged
merged 1 commit into from
Dec 17, 2017

Commits on Dec 17, 2017

  1. Adopt assembly versioning scheme 'major.minor.0.0'

    The rationale behind this is that we don't want changes in the patch
    version to result in a different strong name; patches should be in-
    place updates and shouldn't lead to version conflicts.
    
    This will help reduce the need for assembly binding redirects.
    
    For now, we only do 'major.minor.0.0' instead of 'major.0.0.0' (which
    would be even better).
    
    For the next release, we'll have to increase the minor version by 1
    to rule out strange-looking binding redirects like these:
    
        4.0.0.0 - 4.7.145.0  ->  4.0.0.0
        4.0.0.0 - 4.7.145.0  ->  4.7.0.0
    
    In both cases, the following will probably look less suspicious:
    
        4.0.0.0 - 4.7.145.0  ->  4.8.0.0
    
    Moq 5 will be able to safely make the switch to 'major.0.0.0'.
    stakx committed Dec 17, 2017
    Configuration menu
    Copy the full SHA
    ef1a592 View commit details
    Browse the repository at this point in the history