ScriptRegistrar and StyleSheetRegistrar

[Alec]

While I can understand some of the reasoning behind not bringing them along into Kendo UI, I believe they still have a very useful function. 

1. Not everyone is going to be quick to move the MVC 4, so they would not benefit from the built in minification and bundling.
2. The .OnDocumentReady method of ScriptRegistrar is very useful for combining your document.ready code into one rather than scattered throughout your page.
3. While a lot of people applaud the effort of MS to add Bundling and Minification, using it is no where near as friendly to use as the Telerik StyleSheetRegistrar and ScriptRegistrar.

So how about it Kendo / Telerik? Why don't you include these?

Thanks
Alec

[Atanas Korchev]

Hi,

 There are at least a few ways to implement compression and bundling in an ASP.NET MVC application. We decided not to include a ScriptRegistrar and StyleSheetRegistrar in Kendo UI for ASP.NET MVC because they would not provide such a great benefit over the built-in web server compression or ASP.NET 4.5 bundling. Perhaps OnDocumentReady is one of the few advantages. However you can easily implement the same with either content placeholders (in WebForms views ) or sections (in Razor views). 

All the best,
Atanas Korchev
the Telerik team

[Vesselin Obreshkov]

You can also use the ones that come with the Telerik MVC Extensions until you migrate to MVC4. We're currently slowly migrating a large project which uses both Telerik and Kendo and we still use the StyleSheetRegistrar and ScriptRegistrar with our MVC3 projects.

[Alec]

Atanas,
    I completely understand _why_ you guys decided against bringing them over. I'm okay with that, but I still think there is a case for having them as I laid out in orignal post. I do not think you are going to see massive jumps to MVC 4 like we saw with MVC 3. MVC 3 was really the first version a lot of the traditional MS developers started using. Prior to that, it seems most were content to think of MVC as a passing fad. 

Also, the point of Kendo was originally to bring all the resources we normally add to a project and consolidate them, this seems to break that original spirit. There are many ways to do it, but you guys had the best way of doing it in my opinion. Take it as a compliment that people still want this. As I pointed out already, the 4.5 bundling it nice, but way too much work to do custom scripts when it was just a couple of method chains / lines in Telerik MVC. 

Vesselin,
    That is what we are currently doing as well. I've not seen anything in MVC 4 that is super compelling to make me move any projects that I have currently use MVC 3. The Web API is exciting, but I personally do not have a need for it...yet. To be honest, I prefer to use kendo with the telerik script and stylesheet registrars. 

Thanks for hearing me out.
Alec

[Atanas Korchev]

Hello Alec,

 As Vesselin said you may continue using the StyleSheet/ScriptRegistrar from Telerik Extensions for ASP.NET MVC as long as you want.

 I would like to point out that ASP.NET bundling is not an ASP.NET MVC 4 feature - it is part of ASP.NET 4.5. As such you can continue using ASP.NET MVC 3 and just change the .NET version in order to benefit from the built-in bundling.

Regards,
Atanas Korchev
the Telerik team