ASP.Net ClientDependency Framework

Make your user/composite controls dependent on JS/CSS client files without worrying about duplicates... Like SciptManager but WAY better. Plus you get combining, compression, minification and output caching out of the box. It's Provider model driven so completely extensible.

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 is exactly what the ASP.Net ClientDependency framework was created for (amongst many other things)

This project includes support for:

  • ASP.Net MVC Framework
  • Provider Model so you can choose how you would like your JS and CSS files rendered
  • Provider Model so you can choose how you would like your JS and CSS files combined, compressed & minified
  • Make your controls dependent on client files by:
    • Attributing your controls
    • Using the JSInclude or CSSInclude web controls
    • Dynamically registering them in code
  • Combining, compressing & minifying JavaScript and CSS files
    • Also, compressing & minifying JavaScript and CSS files that are found directly in the markup without being registered with ClientDependency framework (these files are termed 'Rogue' files in this framework)
  • Resolving the correct URL paths in CSS files while they are being combined so you don't have to worry about this
  • Combining external (not stored on your server) JS and CSS files into the same bundle as your local files
  • OutputCaching of the combined/compressed composite files
  • Saving of the combined/compressed composite files for increased performance when applications restart or when the Cache expires
  • Creation of an XML file map to tell you which saved composite files are for which real files
  • Easily clearing the cache
  • Versioning the files
  • Tagging client files with priorites
  • Tagging client files with path names so you don't have to worry about moving files around in your project, worrying about absolute vs relative paths, or running your application in a virtual folder

 

 

Download Now!