NumericUpDown: Bug fix [14622]: When defining the properties for the NumericUpDown, if you define the Value property before the Maximum and Minimum properties , the Spiners will not eveluate the Max/Min value properly. If you don't want to compile the source for the fix, just be sure to define all properties prior to setting the Value property.

ExtendedWPFToolkitSolution/Src/WPFToolkit.Extended/NumericUpDown/NumericUpDown.cs

@@ -19,11 +19,14 @@ namespace Microsoft.Windows.Controls
 
         private static void OnMinimumPropertyChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
         {
+            NumericUpDown nud = d as NumericUpDown;
+            nud.SetValidSpinDirection();
         }
 
         protected virtual void OnMinimumChanged(double oldValue, double newValue)
         {
         }
+
         #endregion Minimum
 
         #region Maximum
@@ -37,6 +40,8 @@ namespace Microsoft.Windows.Controls
 
         private static void OnMaximumPropertyChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
         {
+            NumericUpDown nud = d as NumericUpDown;
+            nud.SetValidSpinDirection();
         }
 
         protected virtual void OnMaximumChanged(double oldValue, double newValue)