Introduction - If you have any usage issues, please Google them yourself
When working in teams or when people are able to publish add-on components for your project, it becomes very cumbersome to try to ensure that you are not loading duplicate JavaScript files or CSS Stylesheets. It would be much nicer to just tag your control as being dependent on specific client files and not worrying about if they ve already been included with a page or other files. This was the primary reason why the ASP.Net ClientDependency framework was created. ClientDependency also manages all of the script/style file compression, combination, minification and persistence for you. It will even detect and process script/styles that aren t registered with the framework and other requests such as json that can be minified/compressed. All of this is fully configurable if you need to modify the default behavior.