Scheduler component WPF vis a vis ASP.NET

[Richard]

Hello.

We are thinking of upgrading from UI for WPF to DevCraft.UI.

The main driver behind this is to migrate our scheduler application.

So my question is: do I have the same features on the ASP.NET.Core scheduler component?

Is there something I will miss in the net.core component, other than the technology gap?

We make good use of: custom appointment, custom edit template, custom slots with special slot style selector, custom resources, paged list implementation of IPagedCollectionView and RadPager, recurrence, drag and drop, as well as custom filtering and ordering,  and so forth.
Is there something I will miss in the net.core component, other than the technology gap?

Thanks

[Richard]

I Should add that the same question applies to the alternative of using Angular, of course.

[Vladimir Stoyanov]

Hello Richard,

Please, check out the UI for ASP.NET Core Scheduler documentation - here. You can also check out the Kendo UI for Angular Scheduler documentation. 

If you have specific questions regarding one of the two technologies, you can open a new forum thread in the corresponding forum: UI for ASP.NET Core Forum, Kendo UI for Angular Forum. 

I hope you find this information helpful.

Regards,
Vladimir Stoyanov
Progress Telerik