Comments on: 20 Tips to Improve ASP.net Application Performance

By: puma boots

puma boots — Fri, 05 Feb 2010 08:22:33 +0000

Typing a train a letters also has a crazy delay although significant improvement. How do I solve that?

By: Tom G

Tom G — Tue, 01 Dec 2009 17:32:45 +0000

Bookmarked here --> http://www.codebounce.com/ASPNET

By: Ron

Ron — Fri, 18 Sep 2009 10:02:22 +0000

My pages has lots of gridviews. Turning off Trace improves development speed. However, this is not enough. Typing a train a letters also has a crazy delay although significant improvement. How do I solve that?

By: nutan

nutan — Fri, 21 Aug 2009 09:49:05 +0000

All these points are very useful.
Thank You.

By: Umar J

Umar J — Wed, 01 Jul 2009 07:53:36 +0000

you should not use client-side validation because a potential attacker can easily disable javascript and send malicious data to your web site. ALWAYS USE server validation AND client-side validation (because it is more user-friendly and users can check their data as they're writing it without waiting for the postback)

By: Custom cars

Custom cars — Fri, 01 May 2009 06:16:40 +0000

Gr8 job man…Such a gr8 posting these are the best 20 tips improve ASP.

By: Kris van der Mast

Kris van der Mast — Thu, 16 Apr 2009 07:42:39 +0000

On tip 19: There's also an alternative by using the using keyword: http://msdn.microsoft.com/en-us/library/yh598w02….

By: Improving ASP.NET performance « Small Business+Phoenix+Software

Improving ASP.NET performance « Small Business+Phoenix+Software — Sat, 01 Nov 2008 15:46:31 +0000

[...] ASP.NET performance Ran across this nice post today on tips for improving ASP.NET performance, why not [...]

By: shan

shan — Tue, 29 Jul 2008 15:04:56 +0000

Nice article. Thank you

By: Sathya

Sathya — Wed, 26 Mar 2008 13:20:11 +0000

A very good article. However, in tip 18, “Use ControlState and not ViewState for Controls”, you may probably want to add that it is not a substitute for viewstate. The underlying mechanism to persist controlstate is identical to viewstate (and consequently it has same drawbacks). ControlState should be used judiciously and only for data that needs to be persisted across postbacks irrespective of whether viewstate is enabled or not.

By: Ally

Ally — Sat, 01 Mar 2008 04:25:54 +0000

It better to use both client-side and server-side validations because the client-side will only reduce the trips made when the user input wrong data but if the user bypasses it then server-side validations is very important.

By: sivakumar

sivakumar — Thu, 29 Nov 2007 07:46:13 +0000

need detailed info on tip no 4 . why datagrid controls are not good to use ?

By: Ramesh

Ramesh — Fri, 16 Nov 2007 16:02:16 +0000

Hai .. nice article , don’t get back by the negative feedback , its a part of a article , put something like this … so people start thinking about performance of ASP.NET and etc …

By: kalika prasad

kalika prasad — Fri, 02 Nov 2007 13:23:44 +0000

hello sir ,

u have to be send many tips nd did use thanx alot for it. i like nd have taken benifit from it.

By: sylv3rblade

sylv3rblade — Mon, 17 Sep 2007 15:22:03 +0000

Although I’ve stopped developing in ASP, I found some of of the tips simply indispensable. ~kudos to you~

By: sadegh

sadegh — Thu, 06 Sep 2007 19:03:23 +0000

very good article , thanke you.
http://www.FirstDL.com

By: Gubatron

Gubatron — Thu, 06 Sep 2007 05:32:31 +0000

“Avoid server side validations”

Be ready to get your server side application to be hacked in every possible way

By: John Puddifoot

John Puddifoot — Wed, 05 Sep 2007 10:23:30 +0000

Just to expand slightly on what most of the comments here are referring to on point 3 for any users that aren’t aware of the potential impact of this move.

Server side validation on data collection isn’t optional in any way. The result of removing it is exposing your website/application to errors and, in cases, hacking. As described above, many users don’t have (or allow) cilent-side scripts running within their browser – meaning in these cases, client side validation doesn’t occur. So exmaples here would be the data could easily be incorrectly entered.

Worse than this however is the hacking element. Poorly protected scripts can be exposed to attacks such as SQL Injection (http://en.wikipedia.org/wiki/SQL_injection). It is true that Server Side validation alone will not protect you from this, and that there is a great deal of inaccurate information regarding it, however by exposing your site to unvalidated data, this is another thread. There are more problems (for instance if you allow users to send tags to the server without handling these). It’s a big old area to go into, but #3 is a definate no-no in my book.

Miguel’s second post about using both is far better. This doesn’t rely on client side code, it makes use of it if possible and both improves the responsiveness of the site to the user and reduces workload on the server (as the server will receive less unvalidated requests). It will however still receive some unvalidated requests – and this is when the Server Side checking kicks in.

Other than that, some interesting suggestions, but would benefit from further info and links to more sites for each point.

By: Miguel Carrasco

Miguel Carrasco — Tue, 04 Sep 2007 22:59:04 +0000

Hi everyone! I have posted a follow up to this article, I hope you enjoy the read!

http://www.realsoftwaredevelopment.com/2007/09/aspnet-performa.html

Thanks,

Miguel

By: Jason Maletsky

Jason Maletsky — Tue, 04 Sep 2007 19:49:29 +0000

I think (and hope) that he is saying to not use only server side validation, but a combination. Only crazy people would rely just on the client.