Look at the emerging WASM projects such as Blazor or Ooui. The obvious path seems to be to have a strong HTML based suite, i.e Kendo, ported to Blazor. However another option would be to improve the Xamarin forms components to have comparable functionality to their desktop counterpartys so they can be used in LOB applications under Ooui. The current Xamarin components are too mobile centric. A third option, which admittedly seems like a bit of a long shot at present, would be to take Moonlight, strip out the plugin stuff, strip out all but the layout code, and redo that to write to an HTML Canvas. Now that's probably outside your scope although in my opinion its the most attractive of the 3 options. In summary I suggest you look at providing a full featured UI component suite that runs under wasm.
MS said server-side blazor is planned for .net core 3 in 2019 (https://www.youtube.com/watch?v=7Eh_l7jEcCo)
Client-side will take longer.
Could you add kendo components support for sever side blazor?
add kendo support for blazor server-side that is now available in 0.5
Uno Platform should also be in the list of wasm frameworks under consideration especially as its actively developed and Ooui seems a bit dormant.
Thanks for all of the feedback shared so far around Blazor and Ooui support! We're very excited about these frameworks as well and are actively looking in to what we can do in terms of support.
One thing to keep in mind is that these frameworks are still fairly young (Blazor is on 0.4.0) so there are some gaps that need to be filled before we can start targeting these frameworks with some of our more complex components.
Keep on voting and providing feedback here and we'll keep everyone up-to-date around the support for these frameworks through this feedback item!
why not port the most used kendo components to blazor and release kendoui for blazor experimental and see adoption? I would love to see Grid, DropDownList and some basic charts for Blazor.
Jason Craig commented
With the release of .Net Core 3 Microsoft has stated they are including open source WPF and Winforms. The Avalonia team said their XAML implementation should port to Mono/WASM with a few tweaks to the WASM and WebGL specs.
As soon as this is done there should be no problems porting the HWND (Winforms) and DX9 (WPF) dependencies to WASM.
Please provide us a roadmap for us to see when we can expect Telerik Mono/WASM components.
Ooui (Wasm/Forms) is more or less a translator from XAML to HTML. Telerik is the master of both. There is only one company which is able to prepare the best HTML/CSS controls based on XAML (doesn't matter Xamarin.Forms or Silverlight XAML 'standard'). This company is Telerik/Progress.
I wish all great Telerik Silverlight controls were ported to Xamarin.Forms set of controls. In conjunction with Ooui (Wasm/Forms) and some data access libraries it would be a great replacement for Silverlight.
WASM is best thing that has happened in last years for .net developers. Pleaso do both and create enterprise components that can be used in Blazor grid/table,charts, etc and also for xamarin.forms ooui.
Maybe you can start with blazor wrappers for current js components and then move to rewrite in wasm for better performance.
We'd prefer Telerik controls in a XAML based framework, but Blazor is a great step in that direction.
The ideal thing for companies that develop Desktop applications is to use Ooui with Xamarin Forms and third party companies to develop their controls (Grids, Ribbons, etc.) for Xamarin Forms and that these user interfaces can run in a browser (WASM and Ooui).
Ivan Danchev commented
Thank you for logging this feature request. We will investigate the possibilities for integrating our products with WASM.
+3 add Blazor UI components