Strange behaviour in some validations

Mar 1, 2013 at 10:57 AM

We use version 1.0 and 1.1 of the DLL's.
In some situations the validation throws the following error:

"Collection was modified; enumeration operation may not execute."
Stack Trace:
em MvvmValidation.ValidationHelper.<>c__DisplayClasse.<>c__DisplayClass10.<ValidateInternalAsync>b__9()
em RootModuleCabecalho.RootModuleCabecalho.vmPerfis._Closure$__14._Closure$__15._Lambda$__79(ValidationResult a0)
em RootModuleCabecalho.RootModuleCabecalho.vmPerfis._Lambda$__78() em MvvmValidation.ValidationHelper.GetResult()
em MvvmValidation.ValidationHelper.GetResultInternal()
em System.Collections.Generic.Dictionary`2.ValueCollection.Enumerator.MoveNext()

Internal error:
System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
em MvvmValidation.ValidationHelper.<>c__DisplayClass15.<ExecuteValidationRulesAsync>b__14(Object _)

The validation works correctly but do not understand why this error happens. Have you any idea what could be?

Mar 1, 2013 at 3:32 PM

It looks like a concurrency bug. Probably multiple validations happen at the same time. I will investigate.
Oct 22, 2013 at 8:54 AM

i have another bug to report on that.
in my project i dont recieve the resultchanged event on the ValidationHelper in C#
But in it works good.
shouldn't be a difference between these 2 technologies isnt it?