This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
Avoid using the call to System.Diagnostics.Requires #79
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Newer versions of VS are having issues with CCRewrite and it turns out this is something that is going to die out in the future as Microsoft is reluctant on maintaining this. (see microsoft/CodeContracts#476)
This PR implements the
System.Diagnostics.Requiresfunctions in the Requires class. Since this is in the same namespace as the other classes, all the existing calls toSystem.Diagnostics.Requiresare redirected to this implementation. As a result, the CCRewrite is no longer required to be installed on machines wanting to use this framework which simplifies development (and deployment) a lot. It also fixes the issue discussed on #42