Matt

Nice blogpost – I’m just getting started with LESS and I’ve read this post to get me started.

However it seems to me that dotless provides one the option to decide if the stylesheet should be cached and minified or not?

Right now I’m not sure I get why I should use clientdependency since it seems to me that caching and minifying comes out of the box?

Am I missing something obvious?

Matt

Personally, I’m not using Client Dependency on the front end of my sites, this post was more a “this is how you could do it” as an alternative to Stefan’s post. .less does have some caching built in, so will create a dependency on the .less file. If that file changes, then it’ll update it’s cache. In this case, the only benefit to using Client Dependency would be to merge multiple files and/or compress file contents, which for me, isn’t really an issue ATM.

Cheers

Matt

Great post, many thanks.

I’ve been using .less for a while and found it super useful.

I’m a little confused though, as you now say you don’t use client dependency on the front end. If so how are using it, if at all? (you seem to be using it in your original post)

My main concern is that the CSS files are getting ‘built’ on each load, not sure if .less deals with this side automatically?

Appreciate your thoughts.

Cheers

Rich

Thanks. It was using client dependency with the .less.CSS that I was having problems with. So I only ended up using it for .ja as suggested

Cheers

Ben

I use .less.css all the time. You should just need to change the path for the HTTPHandler to *.less.css (I don’t tend to use client dependency on the front end, so I don’t worry about the client dependency steps)

Have you made sure you’ve changed the right path attribute? (ie both the IIS6 and IIS7 definitions)

I end up with a blank CSS file

Cheers

I’ve updated the link in the post.

Still alive and kicking.