Telerik already provide PDF Viewer for Silverlight, this control is very common used and safe our time to display PDF without using client's browser plugin. It will be great this control to be available in ASP.NET, we will not spending IT budget for another controls. Telerik we know you can do it, this will make you more competitive.
Update from 4 Oct 2017: You can find a sample implementation of a CDN fallback in the following code library project: http://www.telerik.com/support/code-library/cdn-fallback You can try implementing a fallback similar to the approach from the links below, but check for the window.$telerik variable and initiate a postback to change the web.config or the concrete page's properties to avoid the CDN. You can find a sample implementation attached below. - http://www.hanselman.com/blog/CDNsFailButYourScriptsDontHaveToFallbackFromCDNToLocalJQuery.aspx - http://docs.telerik.com/kendo-ui/intro/installation/cdn-service#refer-kendo-ui-from-cdn-with-local-script-fallbacks Alternatively, use a custom CDN of your choice that will be better for your case/have better uptime than Amazon CloudFront: http://docs.telerik.com/devtools/aspnet-ajax/controls/scriptmanager/cdn-support/custom-cdn-provider
Add functionality in the VSB to generate a dll file based on the created resources for custom skin.
You can hide certain characters using "*" in the DisplayMask. For example: Mask="####" DisplayMask = "**##" If the value is "1234", after blur it will look like "**34" The same approach can be used for all mask parts. The only requirement is DisplayMask to be longer or equal to the Mask. For example: Mask = "<1..999>someLiterals####SomeMoreLiterals<3..123>" DisplayMask = "***someLiterals**#*Some*******s<1..99>*" If in the above example the DisplayMask is shorter or does not contains enough asterisks to match the editable parts, the visible value on blur can be wrong.
Since Responsive Design is the actual trend, and most of the free frameworks have compatibility issues with Telerik Controls due to the Global Styles, I suggest a new Responsive Framework. A Telerik Responsive Framework, that out of the box would work perfectly with all the Telerik suite. I believe that this would be very appreciated by all your customers. Some of the controls should also be prepared to work with this framework resizing it's elements according to the device.
TypeScript declarations for the ASP.NET AJAX controls will be of great help for developing projects in TypeScript. See this forum thread for more information: http://www.telerik.com/forums/typescript-declarations
NOBODY supports this turd of a browser anymore. http://www.buuteeq.com/blog/why-we-dont-support-ie7/ Your css codebase could trim up a ton removing all the crappy hacks. Worked for kendo, and nobody is missing it. I'm sure your developers would have a party (week long) if they could ditch having to support it too. You're such a big market player supporting it just helps ie7 hold on to it's MEASLY <1% marketshare...stop contributing :) Vote now people!