SfNumericUpDown Value is always 0

[Luca]

hi,

can you check why since last release value property is always 0?

thanks

[Luca]

tested the prev version and it is ok, so the bug is just in the last release

[Bharathiraja K]

Hi Alberto, 

 

Greetings from Syncfusion. We have tried to replicate the reported issue at our end by created a sample with the provided information that you mention on your last update, we are afraid that, we are not able to reproduce the issue at our end. 

 

Please find the tested sample below.  

 

Sample Link: http://www.syncfusion.com/downloads/support/directtrac/general/ze/Attribute-364015262  

 

We are not able to reproduce this issue at our end, so can you please revert us by modifying the sample based on your application along with replication procedure. This will be helpful for us to investigate further and provide you a better solution at the earliest. 

 

Regards, 

Bharathi. 

[Luca]

i mean that at code level  property value is always 0 even if the control shows a number.

can you try?

works just till version 16.4.0.54

thanks

[Bharathiraja K]

Hi Alberto, 

  

Sorry for the inconvenience caused.  

 

We were able to reproduce the reported "Public Value property not updated properly" issue at our end and logged a defect report. 

 

Feedback Link:  https://www.syncfusion.com/feedback/5751/public-value-property-not-updated-properly  

 

We will fix this issue and include in our weekly NuGet which is scheduled to be release on 23^rd April 2019.  

  

Regards, 

Bharathi. 

[Luca]

thank you.

guys your library are amazing but (my 2 cents) you should improve your test process because often happpen that a new release breaks something.

of course it can happen, but please improve your test phase ;)

[Iyyappan Mani]

Hi Alberto, 

 

We deeply regret the inconvenience. 

  

We used to test our controls manually and through automation before every release to make sure there are no breaks in the existing behavior. 

  

However, in this particular case, we have made some architectural changes for the stability of SfNumericUpDown control and it lead to this break in the behavior. We are continuously working on to ensure seamless upgrade for our updates and we will make sure these kind of issues are avoided in future. 

 

Regards, 

Iyyappan M. 

[Iyyappan Mani]

Hi Alberto, 

  

Thanks for your patience.  

We couldn’t able to move this fix in the promised weekly nuget and hence we have fixed and provided the patch for the reported “Public Value property not updated properly“ issue and it can be downloaded from the below link.  

Please find the patch setup from the below location.  

http://syncfusion.com/Installs/support/patch/17.1.0.38/916885/F143841/SyncfusionPatch_17.1.0.38_916885_4232019095852510_F143841.exe  

or  

  

Please find the patch assemblies from the below location.  

http://syncfusion.com/Installs/support/patch/17.1.0.38/916885/F143841/SyncfusionPatch_17.1.0.38_916885_4232019095852510_F143841.zip  

or  

  

Please find the NuGet from the below location.  

http://syncfusion.com/Installs/support/patch/17.1.0.38/916885/F143841/SyncfusionNuget_17.1.0.38_916885_4232019095852510_F143841.zip  

Assembly Version: 17.1.0.38  

   

Disclaimer:  

Please note that we have created this patch for version 17.1.0.38 specifically to resolve the issue reported in the forum 143841. If you have received other patches for the same version for other products, please apply all patches in the order received. This fix will be included in our next weekly NuGet release which is scheduled to be rolled out on April 30^th  2019. We appreciate your patience until  

Note: 

Could you please follow the below steps before applying the patch clear the Nuget cache in your machine and check.  

KB: https://www.syncfusion.com/kb/6987/how-to-clear-nuget-cache   

 

Regards, 

Iyyappan M.