Hi,
After the installation of Windows 10 Anniversary Update (1607) we observed that the rendering of the SchedulerView control in our application is broken. Especially the display of Resources is affected (e.g. Resource headers are multiplied randomly on the whole control). We installed the .NET 4.6.2 on some older system and got the same problem. I found information about the changes in .NET 4.6.2 https://msdn.microsoft.com/en-US/library/ms171868(v=vs.110).aspx#WPF462. It seems the guys at Microsoft did some changes to the group sorting area. My question is - did anyone experience similar issues after the recent updates? Any hints are appreciated.
12 Answers, 1 is accepted
We are not aware of the explained issue - can you please provide a sample project demonstrating the issue?
Also can you share some more details regarding the issue - did you modified the project somehow (changing the target framework version to 4.6.2) or this happened without any changes on the project (only by installing the Windows 10 Anniversary Update)? Can you also provide a screenshot of the issue?
I'm looking forward to hearing from you.
Regards,
Kalin
Telerik by Progress
Rank 1
Hi Kalin,
Thx for the response. I am not able to create the test project at the moment, but it may well be that the issue is related to one of the customizations we made. I have yet to dig into this more carefully.
The project is compiled under .NET 4.0 (we still have to support some legacy XP machines). As soon as the app is run on .NET 4.6.2 the problem occurs. I attach the screenshot. Btw - the Appointments seem to render just fine.
Best Regards,
Grzegorz
We just found an issue related to the .Net 4.6.2 and recycling of the GroupHeaders that might be causing the observed behavior on the screenshot. The fix will be available with the next official release (mid September), so once it is live please test it and let us know if it resolves the problem on your side.
I'm looking forward to hearing from you.
Regards,
Kalin
Telerik by Progress
Quick follow up - the fix will be also available in the next internal build. You would be able to download it next Monday from your Telerik account.
Please test it and let me know if the issue is resolved.
Regards,
Kalin
Telerik by Progress
Rank 1
Thanx for the quick reaction. The thing is we use customized version of the components from Q22013 (XAML and programming model modifications) and we already knew that any upgrade is going to be painful. I'll let you know once I check if we are able to use the fix.
Regards,
Grzegorz
If you need further assistance during the upgrade process, please do not hesitate to contact us - we will be glad to help.
I'm looking forward to hearing from you.
Regards,
Kalin
Telerik by Progress
Rank 1
We have also modified the source code for one of our legacy applications and are having the same issue. Could you let us know what changes were made so that we might input those changes into our code and fix the issue.
Thanks!
I already replied in the support ticket regarding the same question.
If you have any other questions, please let us know.
Regards,
Kalin
Telerik by Progress
Rank 1
Hello Kalin,
I finally got some time to have a look at the issue again. Does the Q32016 release contain the fix you mentioned? Since we currently don't do any active development on this project (and therefore have no active subscription) I tried the trial version of Q32016 but it doesn't seem to solve the problem.
Best Regards,
Grzegorz
Yes, the fix was included in the R3 2016 release. If you can open up a support ticket and provide a sample project demonstrating the issue, we will be glad to check it on our side and investigate the observed issue.
I'm looking forward to hearing from you.
Regards,
Kalin
Telerik by Progress
Rank 1
Hi Kalin,
Sorry for the confusion I created - I must have had a bad day, I tested the wrong version. The Q32016 components SOLVE the issue, everything seems to be working fine. We are in the process of upgrading. We are also evaluating the best licensing option for us. Huge thanks for your help :).
Best Regards,
Grzegorz
I'm glad the issue on your side is resolved. If you have any other questions or concerns, please do not hesitate to contact us.
Regards,
Kalin
Telerik by Progress