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

Verify.NotDisposed ambiguous or misleading parameter names #33

Closed
mwpowellhtx opened this issue Jul 31, 2019 · 2 comments
Closed

Verify.NotDisposed ambiguous or misleading parameter names #33

mwpowellhtx opened this issue Jul 31, 2019 · 2 comments
Labels

Comments

@mwpowellhtx
Copy link

In Verify.NotDisposed(bool condition, string message), string message does not appear to be a message at all, but rather an object name, at least according to the error:

Cannot access a disposed object.
Object name: '...'

Reporting only the leading indicator, smoke test if you will. Review comprehensively for the extent of the issue.

@mwpowellhtx
Copy link
Author

My assessment would be that the exception messages seem inconsistent at best.

@AArnott
Copy link
Owner

AArnott commented Sep 25, 2020

It appears to only be that specific overload that was faulty. Fixed in #40.

@AArnott AArnott closed this as completed Sep 25, 2020
@AArnott AArnott added the bug label Sep 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants