Please explain what it does in more detail as I guess that there's a few (besides me) that don't understand what this does? To be honest I dont know what "Client Dependency cache" is but it sounds like your solving a problem regarding editing files direcly (outside Umbraco)? But edit script files directly - we couldnt already?
Umbraco 4.5 comes with the Client Dependency Framework pre installed. The Client Dependency Framework compresses and caches css and js dependencies. It's mainly used by the Umbraco UI, but you can can also use it on the front end to compress your UI's css and js files. The main problem with the Client Dependency Framework as it stands though is that it basicaly caches your dependencies on first use and any further requests uses the cached versions, regardless of whether those files have changed in the mean time. The only way to invalidate the cache is to increase the version number and delete the ClientDependency folder by hand.
What this package does is remedy this problem, it basically watches the /css and /js folders for any changes (whether that be via the file system or the UI) and automatically increaes the version number and deletes the ClientDependency folder if any changes are detected.
This makes using the Client Dependency Framework for front end dependency caching much more usable.
Does anyone have any detailed information on how or why the Client Dependency Framework when using it with the loader control along with enabling the Rogue File detection in the configuration seems to break the following items being output to the page from XSLT macros:
1. Macros that output javascript files to the page using the Umbraco.Library:RegisterJavascript function (these scripts do not get output to the page when client dependency is running with the loader control)
2. Macros that output inline css styles for setting background images on elements that are to be used in conjuction with Jquery. These items are also completely broken and the UI does not render correctly when Client Dependency is enabled / Rogue File detection is enabled.
Any details on how to make this work or if it is even possible would be very helpful. Also any other forums, threads, or blogs about this would work too. I have already done extensive research on codeplex and the documentation found there does not seem to have any information to the issues I am experiencing.
I am running multiple sites from one umbraco instance on the Umbraco 4.7 platform. Please help!
Sounds cool
Please explain what it does in more detail as I guess that there's a few (besides me) that don't understand what this does? To be honest I dont know what "Client Dependency cache" is but it sounds like your solving a problem regarding editing files direcly (outside Umbraco)? But edit script files directly - we couldnt already?
Best,
Jesper
Hey Jasper,
Umbraco 4.5 comes with the Client Dependency Framework pre installed. The Client Dependency Framework compresses and caches css and js dependencies. It's mainly used by the Umbraco UI, but you can can also use it on the front end to compress your UI's css and js files. The main problem with the Client Dependency Framework as it stands though is that it basicaly caches your dependencies on first use and any further requests uses the cached versions, regardless of whether those files have changed in the mean time. The only way to invalidate the cache is to increase the version number and delete the ClientDependency folder by hand.
What this package does is remedy this problem, it basically watches the /css and /js folders for any changes (whether that be via the file system or the UI) and automatically increaes the version number and deletes the ClientDependency folder if any changes are detected.
This makes using the Client Dependency Framework for front end dependency caching much more usable.
Matt
Thanks for taking your time to explain this. Great idea. I'll add this package to my loooong list of Packages to install in every solution.
Thanks and have a nice weekend
Jesper
ps. If I promise not to call you Mutt, could you then call me Jesper :-)
Haha, lol sorry Jesper, I'll pay more attention next time =)
Mutt
Does anyone have any detailed information on how or why the Client Dependency Framework when using it with the loader control along with enabling the Rogue File detection in the configuration seems to break the following items being output to the page from XSLT macros:
1. Macros that output javascript files to the page using the Umbraco.Library:RegisterJavascript function (these scripts do not get output to the page when client dependency is running with the loader control)
2. Macros that output inline css styles for setting background images on elements that are to be used in conjuction with Jquery. These items are also completely broken and the UI does not render correctly when Client Dependency is enabled / Rogue File detection is enabled.
Any details on how to make this work or if it is even possible would be very helpful. Also any other forums, threads, or blogs about this would work too. I have already done extensive research on codeplex and the documentation found there does not seem to have any information to the issues I am experiencing.
I am running multiple sites from one umbraco instance on the Umbraco 4.7 platform. Please help!
is working on a reply...