When the Scheduler control is bound a datasource that includes a Boolean value/column in the database the Spreadsheet column presents this as "true" or "false" strings.
Allow alternate strings such as "Yes" or "No" to represent a Boolean. Would of course need to update the datasource appropriately on Edit of a cell that uses this presentation.
Hello, I did not see this in any of the examples, or I just missed it. With this control, are you able to use an editor template for the fields you add? A lot of my existing forms, I use an editor template for the fields, but I don't see that option here. For example, I have a editor template defined for use of Date/Time fields that has the settings defined that I want to use throughout the website.
Can this be done using the form component?
Using Visual Studio Enterprise 16.0.0.
Created MVC Project 4.6.1
Run Telerik utility to "Convert to Telerik Web Application" from Project context menu. On a clean project just created from the VS Template.
Since previous step errors out and doesn't complete an attempt was made to use the Telerik Upgrade Wizard.
This produced the following error:
An error occurred while running the wizard. Error executing custom action Telerik.VSX.Actions.ShowConversionLogAction: Could not instantiate a TextTransformation object from the compiled assembly. The following Exception was thrown: System.InvalidCastException: Unable to cast object of type 'Microsoft.VisualStudio.TextTemplating3e7341780e3e4a17bdabe17b447cd796.GeneratedTextTransformation' to type 'Microsoft.VisualStudio.TextTemplating.TextTransformation'. at Microsoft.VisualStudio.TextTemplating.TransformationRunner.CreateTextTransformation(String fullClassName, ITextTemplatingEngineHost host, Assembly assembly, ITextTemplatingSession userSession)
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.