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

FluentValidation 10.2.0 causes MissingMethodException in Blazored.FluentValidation #69

Closed
benghaner opened this issue May 29, 2021 · 2 comments · Fixed by #70
Closed
Labels
Bug Something isn't working

Comments

@benghaner
Copy link

benghaner commented May 29, 2021

Describe the bug
FluentValidation 10.2.0 causes the following MissingMethodException in Blazored.FluentValidation:

System.MissingMethodException: Method not found: 'FluentValidation.AssemblyScanner FluentValidation.AssemblyScanner.FindValidatorsInAssembly(System.Reflection.Assembly)'.
at Blazored.FluentValidation.EditContextFluentValidationExtensions.GetValidatorForModel(IServiceProvider serviceProvider, Object model, Boolean disableAssemblyScanning)...

To Reproduce
Steps to reproduce the behavior:

  1. Install Blazored.FluentValidation 2.0.0 and FluentValidation 10.1.0.
  2. Setup a Blazor form using fluent validation. The samples provided with this repo will work.
  3. Launch the app and submit the form, no issue.
  4. Upgrade to FluentValidation 10.2.0.
  5. Launch the app again and submit the form. The exception occurs.

Hosting Model (is this issue happening with a certain hosting model?):

  • Tested using Blazor Server

Additional context
Probably caused by: Pull request 1742 Support Internal Types In AssemblyScanner

@benghaner benghaner added Bug Something isn't working Triage Issue needs to be triaged labels May 29, 2021
@xevimayo
Copy link

xevimayo commented Jun 9, 2021

This issue is very important to fix. When you install packages from Nuget in a clean project it just doesn't work at all and appears the error because nuget install FluentValidation 10.2.0. I spend one entire morning figuring out what was happens, till I found this issue.

@chrissainty
Copy link
Member

Apologies for the delay on this one, folks. It's now going through to NuGet and should be available in the next 15-20 minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants