Comments on: ASP.Net 4.0 features http://sorin.serbans.net/blog/index.php/2009/06/26/aspnet-40-features/ Look at the spoon ... There are no bugs Sun, 27 Nov 2011 09:32:30 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Cristian O. http://sorin.serbans.net/blog/index.php/2009/06/26/aspnet-40-features/comment-page-1/#comment-4540 Cristian O. Fri, 28 Aug 2009 07:16:50 +0000 http://sorin.serbans.net/blog/?p=113#comment-4540 Some features look nice, here's a personal oppinion: - Extensible Output Caching I don't really think I've used output caching. In enterprise applications I've always had requirements for the data to be immediately available and the OOTB asp.net caching didn't fit my needs, that's why custom caching mechanisms may sound pretty cool. - Auto-Start Web Applications Nice but not that useful - Client Template Rendering Definitely something to consider. I am an adept of using more resources on the client side and use the server only to provide / process data based on rules. - Instantiating Behaviors and Controls Declaratively I'm not sure how this affects the page load time (on the client side) if you have many controls on it. We'll see how this will turn out, right now I'm a bit worried about it. - Live Data Binding Definitively useful, this should save a lot of javascript code. - Using the Observer Pattern with JavaScript Objects and Arrays Worried about browser performance with more and more code to execute on client side. - The AdoNetServiceProxy Class This seems useless to me, same as ADO.NET Data Services. In a modular enterprise applications, I probably wouldn't use any of them. - The DataContext and AdoNetDataContext Classes How about business rules ? Do we put them in javascript too ? - Refactoring the Microsoft AJAX Framework Libraries (partial includes) Definitely useful. There's no point in laoding js libraries if they are not used. - Setting Meta Tags with the Page.Keywords and Page.Description Properties Little value added - Enabling View State for Individual Controls Interesting. I hate ViewState, the more control I have on it, the better I feel. - Routing in ASP.NET 4.0 Very nice, unfortunately it requires a lot of boring code changes on existing applications - Setting Client IDs Well, this is a huge one. Those ctrl01_ucEditEntity_whereTheHellIAm_damnIGotLostAgain_txtName were the most annoying things in the generated HTML (well maybe sometimes the ViewState, but they definitely had a top spot). With libraries like jQuery, javascript development will be nicer. - Dynamic Data No value for me, I never used it and I probably never will. Some features look nice, here’s a personal oppinion:

- Extensible Output Caching
I don’t really think I’ve used output caching. In enterprise applications I’ve always had requirements for the data to be immediately available and the OOTB asp.net caching didn’t fit my needs, that’s why custom caching mechanisms may sound pretty cool.

- Auto-Start Web Applications
Nice but not that useful

- Client Template Rendering
Definitely something to consider. I am an adept of using more resources on the client side and use the server only to provide / process data based on rules.

- Instantiating Behaviors and Controls Declaratively
I’m not sure how this affects the page load time (on the client side) if you have many controls on it. We’ll see how this will turn out, right now I’m a bit worried about it.

- Live Data Binding
Definitively useful, this should save a lot of javascript code.

- Using the Observer Pattern with JavaScript Objects and Arrays
Worried about browser performance with more and more code to execute on client side.

- The AdoNetServiceProxy Class
This seems useless to me, same as ADO.NET Data Services. In a modular enterprise applications, I probably wouldn’t use any of them.

- The DataContext and AdoNetDataContext Classes
How about business rules ? Do we put them in javascript too ?

- Refactoring the Microsoft AJAX Framework Libraries (partial includes)
Definitely useful. There’s no point in laoding js libraries if they are not used.

- Setting Meta Tags with the Page.Keywords and Page.Description Properties
Little value added

- Enabling View State for Individual Controls
Interesting. I hate ViewState, the more control I have on it, the better I feel.

- Routing in ASP.NET 4.0
Very nice, unfortunately it requires a lot of boring code changes on existing applications

- Setting Client IDs
Well, this is a huge one. Those ctrl01_ucEditEntity_whereTheHellIAm_damnIGotLostAgain_txtName were the most annoying things in the generated HTML (well maybe sometimes the ViewState, but they definitely had a top spot). With libraries like jQuery, javascript development will be nicer.

- Dynamic Data
No value for me, I never used it and I probably never will.

]]>