Get PexProtector
out of the debugger's way
#508
Merged
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.
PexProtector.Invoke
annoyingly breaks step-debugging through affected parts of Moq's source code. This commit solves this (and, besides, reduces object allocations caused by the lambda's variable capturing).Hopefully, at a later point, we can get rid of
PexProtector
entirely. (Is anyone actually using Pex / Smart Unit Tests / IntelliTest these days?)