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

Is Verify() recommended in production environment? #59

Closed
YehudahA opened this issue Apr 4, 2017 · 3 comments
Closed

Is Verify() recommended in production environment? #59

YehudahA opened this issue Apr 4, 2017 · 3 comments

Comments

@YehudahA
Copy link

YehudahA commented Apr 4, 2017

I think that it's important to clarify the cost of verify, it creates all actual types.
For large projects, it is not recommended for production.

@dotnetjunkie
Copy link
Collaborator

The recommendations are simple: Use Verify() until it's not feasible anymore. In case it affects start-up time too much in production, only run it during test and development. If it takes too much time during development, only run it as part of your test suite.

@YehudahA
Copy link
Author

YehudahA commented Apr 4, 2017

OK.

@dotnetjunkie
Copy link
Collaborator

dotnetjunkie commented Apr 4, 2017

But good point. I'll try to incorporate this info in the docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants