Client Side Web Development

Re: best practices for developing ASP.Net controls with client scripting

Haissam — Fri, 13 Oct 2006 06:26:39 GMT

Personally i use external files when i got a large number of javascript written in one webpage, in this way u can make reading and debugging ur code easier then putting them inline.

Happy coding

Re: best practices for developing ASP.Net controls with client scripting

flanakin — Wed, 04 Oct 2006 22:10:03 GMT

Personally, I see three options. In preferencial order, they are (a) a separate JS file; (b) a cache-enabled ASPX file; and, (c) inline scripting. Use a JS file in any case where your script is static. The reason behind this is that modern web browsers will cache these files and ensure your app performs as best as possible -- remember that JavaScript is parsed when executed, so every little bit helps. If you require dynamic content, try putting the script in a separate ASPX page that utilizes cache headers to maximize the cacheability. In the event that you have code that is dependant upon server controls, use inline scripting. Even if you do go this route, tho, I'd suggest calling functions that are specified in cache-controlled locations to minimize page size and maximize performance.

On a side note, if you have no more than 5-10 lines of code, I wouldn't worry about it. Just stick it on the page since that's the simplest method. The real reasons to separate script into its own file is for performance and/or maintainability... well, and all the other *ilities, as well

Re: best practices for developing ASP.Net controls with client scripting

PeterBrunone — Wed, 04 Oct 2006 21:16:56 GMT

It depends on how dynamic the script needs to be. For example, with EasyListBox, I do both; the bulk of the JS is in an external file, but functionality that changes with the page content is rendered inline with the web form.

Cheers,

Re: best practices for developing ASP.Net controls with client scripting

Javier Luna — Wed, 04 Oct 2006 20:31:44 GMT

Hi mark,

I use your second option. A script file that the page can refer it.

Good Coding!

Javier Luna
http://guydotnetxmlwebservices.blogspot.com/

best practices for developing ASP.Net controls with client scripting

markvw — Wed, 04 Oct 2006 19:27:15 GMT

Hello. I was wondering if when developing custom controls in asp.net that need client script if it is better to emit the script inline with the code or to use a script file that the page can refer to. Any ideas would be much appreciated.

Thanks.