Don't you just hate the source control conflicts you get from minified CSS made from LESS with Web Essentials?

When everything gets jammed onto one line it can be painful to clean up in a merge. Well, you really don't have to keep these files in source control to begin with. (As much will solve this problem.) Only the .less files need to be kept in source control while the .css, .css.map, and .min.css files may just be generated. In Visual Studio 2013 if you go to "Options..." under the "TOOLS" menu you will get the "Options" dialog box. At the left menu, if you pick "LESS" under the "Web Essentials" tree you will be able to set the setting for "Compile files on build" to be true at the right pane. This will force the .css, .css.map, and .min.css files to update upon a build. Note that if you pull down fresh code from source control and these files don't exist to being with that you do have to trick them into being there upfront. Do this by just opening all the .less files and adding a superficial change like a line break or something. I know this is ghetto.