-
Notifications
You must be signed in to change notification settings - Fork 48
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
Error in ModelValidatorProvider #12
Comments
I had the same problem when I upgraded my packages with NuGet yesterday. |
I resolved the issue by replacing the dll libaries manual with a version that worked. I Included a link for a version that works for me https://mega.co.nz/#!McBkDSYR!KTrY9rIOEMt0Ny_1xQqRTgPjrCvINg2sirjYjh8wOd0 |
I am also having this issue when I did a fresh install this morning: Server Error in '/' Application. Error activating ModelValidatorProvider using binding from ModelValidatorProvider to NinjectDefaultModelValidatorProvider Activation path:
Suggestions:
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: Ninject.ActivationException: Error activating ModelValidatorProvider using binding from ModelValidatorProvider to NinjectDefaultModelValidatorProvider Activation path:
Suggestions:
|
When i used NuGet to upgrade the following message did appear when using Web API 2.1 and MVC5
Error activating ModelValidatorProvider using binding from ModelValidatorProvider to NinjectDefaultModelValidatorProvider
A cyclical dependency was detected between the constructors of two services.
Activation path:
3) Injection of dependency ModelValidatorProvider into parameter defaultModelValidatorProviders of constructor of type DefaultModelValidatorProviders
2) Injection of dependency DefaultModelValidatorProviders into parameter defaultModelValidatorProviders of constructor of type NinjectDefaultModelValidatorProvider
The text was updated successfully, but these errors were encountered: