Progress® Telerik® UI for ASP.NET MVC Feedback Portal
Back to Feed
Request a Feature Report a Bug
Duplicated
Last Updated: 06 Apr 2020 08:41 by ADMIN
MeMDev1
Created on: 12 Apr 2013 09:25
Category: UI for ASP.NET MVC
Type: Feature Request
5
Serialization support of DataSourceRequest and applying outside of ASP.NET MVC
I would like to see a separate assembly that can be referenced both on ASP.NET MVC and Application server side and that the DataSourceRequest can be transformed into a DataSourceResult on the Application server side and sent back to the website.

At the moment this is not possible due to the non-generic definitions of the DataSourceRequest and DataSourceResult classes. 

Referencing Kendo from the Application server side also requires references to System.Web and others that shouldn't be necessary.

Statically typed transport serialization should be supported, as required by WCF, Message Queuing or even Protobuf. Such transport mechanisms are required by N-Tier environments.

At the moment, if all DataSourceRequest's should be processed on a web server and propietary database licensing is in effect (ex. for MSSQL) where the cost is per port, it would end up being very costly.
Duplicated
This item is a duplicate of an already existing item. You can find the original item here:
Serialization support of DataSourceRequest and applying outside of ASP.NET MVC
3 comments
Grahame
Posted on: 23 Nov 2017 16:45 
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 ?
jean-philippe
Posted on: 22 Nov 2016 15:05 
It would be a nice feature, because the ToDataSourceResult is offering nice paging/grouping/... suport to manipulate paged data out of a given IQueryable.
I would like to use it to in a WCF method accepting a DataSourceRequest and returning a DataSourceResult (withouht the actual serialization wcf problem and without referencing bunch of MVC specific dll in my WCF project)
ADMIN
Brandon
Posted on: 05 Jun 2013 22:44 
if you're looking to use Kendo UI without the assemblies, you can use just the JS itself on your app servers, where needed.
Create an account Log In
View
Type
Status
Category