Last Updated: 25 Mar 2024 13:16 by ADMIN
Created on: 22 Nov 2016 15:11
Category: UI for ASP.NET MVC
Type: Feature Request
Serialization support of DataSourceRequest and applying outside of ASP.NET MVC
Just like posted here (and declined) : http://kendoui-feedback.telerik.com/forums/127393-kendo-ui-feedback/suggestions/3844570-serialization-support-of-datasourcerequest-and-app

I would like to see a portable separate assembly that : 
- can be referenced both on ASP.NET MVC side and WCF server side.
- A DataSourceRequest and DataSourceResult class that serialize well in both SOAP and REST WCF.

Referencing Kendo from the Application server side also requires references to System.Web.Mvc, Razor pages, ... and others that shouldn't be necessary.
Angel Petrov
Posted on: 23 Jul 2021 08:49


Guys we do have a separate package for the DataSource that targets netstandart2.1 and is not coupled to MVC so it can be used in a more flexible manner. More about it you can find here. It should be able to do the job, could you please verify that it meets the purposes? Is there something additional that is needed?

Angel Petrov
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Posted on: 06 Apr 2020 05:37

Hi Kyle,

The current Feature request, as you can see from its status, is not planned to be implemented for the current release cycle. I can see that you already voted for the item. This is what everyone that wants this feature to be implemented should do. The bigger the number of votes is the bigger the chances for the implementation of a given feature request are. 

Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.
Posted on: 29 Mar 2020 21:04
Any update on this?  Grahame?
Posted on: 23 Nov 2017 16:47
I'm in the process of creating a set of extension method for DataSourceRequest that will transform the request into a URI which can then be used to call a backend service from any .NET standard 1.6 client; I'm also looking at breaking out the DataSourceRequest and DataSourceResult into a separate assembly to give a light weight assembly for these DTO types etc. 

I honestly don't know why Progress/Telerik have opted for a single assembly inside of breaking these out to allowing sharing of DTOs across services/layer/components ?