Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to clean up Client Depency filesHow to clean up Client Depency files
Previous
 
Next
New Post
9/21/2012 6:45 PM
 
I've run into the same problem. 31,000 files, 827MB. I've deleted most of the files but haven't deleted the XML file yet as I wasn't sure if that'd break things.

David O'Leary
Efficion Consulting
 
New Post
9/22/2012 3:04 AM
 
just want to say thanks to all of you for this information that you have posted here. Keep it up.
 
New Post
10/16/2012 11:47 AM
 
In an attempt to solve oddities I was seeing with the Client Dependency functionality, I went ahead and deleted the whole /App_Data/ClientDependency folder in one of my sites and now I can't get the Client Dependency stuff working for that site. It's adding ?cdv=44 to all the relevant css and js files no matter what the version number set in the web.config is.

The /App_Data/CientDependency folder was regenerated along with the [Servername]-[GUID]-map.xml file but the map.xml file has no entries in it, just

I've tried syncing the web.config with a site where the client dependency functionality is working correctly but none of the web.config settings seem to make a difference. If I remove the whole client dependency section from the web.config, none of the CDF controlled css or js files are added at all.

I'm at a loss for what else I can try. My guess is that the [Servername]-[GUID]-map.xml file needs to be regenerated properly somehow but I'm not finding any way to do that.

David O'Leary
Efficion Consulting
 
New Post
10/19/2012 5:57 PM
 
I solved my issues with not being able to enable the Client Dependency Framework. I had upgraded to 6.2.3 and it seems that the wiki entry on Enabling The Client Dependency Framework was not longer valid with 6.2.3 (I've submitted changes to the entry so hopefully they'll be approved and made live soon). Under 6.2.x, to enable the Client Dependency Framework you need to go to Host Setting -> Advanced Settings and expend the Client Resource Management section and then select the desired checkboxes there.

Seems like the Client Resource Management stuff in 6.2.3 is much better than in 6.1.x and hopefully it solves the problem with Gigs of files being generated.

David O'Leary
Efficion Consulting
 
New Post
10/19/2012 6:11 PM
 

Yeah there were a number of improvements made that you've just uncovered - off the top of my head:

1. The obvious one - you don't have to mess around in a web.config file to manage the relevant settings anymore. There is a nice easy UI.
2. The settings are stored in the database, so the site doesn't have to do a restart when you change the settings like in previous versions
3. You can implement different settings per portal -- e.g. enabled in one portal, not in another - or different versions in different portals, etc. - by default all portals inherit from the host settings though.

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to clean up Client Depency filesHow to clean up Client Depency files


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out