Hello,
we have attached error after migrating one of our projects from version 2.1 SP2 to last version 2.2 SO 2 Build 2.22.184.0.
The property 'ValidatesOnNotifyDataError' does not exist in XML namespace 'http://schemas.microsoft.com/winfx/2006 ... esentation
The errors happens on compilation and the 2 screens have a datagrid in design and code.
I ask you suggestion on how to go ahead and solve.
Thank you
Compilation error migrating project to last version 2.2 SP 2
Compilation error migrating project to last version 2.2 SP 2
- Attachments
-
- Errors of compilation after migrating to last version
- ErrorMigrationLastVersion_222184_22SP2.jpg (327.22 KiB) Viewed 8299 times
-
- Posts: 137
- Joined: Mon Jun 11, 2012 2:10 pm
Re: Compilation error migrating project to last version 2.2
Andrea,
Just curious, what happens if you change ValidatesOnNotifyDataError to ValidatesOnNotifyDataErrors (add s to end of error)?
Doing a google search, I found the following post: https://social.msdn.microsoft.com/Forum ... ?forum=wpf I've never used this control or received this error, so I don't know if this would help.
Just curious, what happens if you change ValidatesOnNotifyDataError to ValidatesOnNotifyDataErrors (add s to end of error)?
Doing a google search, I found the following post: https://social.msdn.microsoft.com/Forum ... ?forum=wpf I've never used this control or received this error, so I don't know if this would help.
Adam M.
Controls Engineer
FlexEnergy
Controls Engineer
FlexEnergy
Re: Compilation error migrating project to last version 2.2
Hello Adam ,
thank you for your suggestion.
I tried to insert the 's' and also to delete all part ValidatesOnNotifyDataError = "True" but seems that, during Build- compilation the file XAML is changed and return as before as iX wants so the error is still the same.
Do you know if there is some workaround to avoid this?
Andrea
thank you for your suggestion.
I tried to insert the 's' and also to delete all part ValidatesOnNotifyDataError = "True" but seems that, during Build- compilation the file XAML is changed and return as before as iX wants so the error is still the same.
Do you know if there is some workaround to avoid this?
Andrea