Open KernelLeak opened 10 years ago
Looking at MinifyFile in LessProjectCompiler.cs it seems the logic in there is backwards - it first reads the file's contents (to see if they've changed) and only when it knows that the contents have changed it'll check if the file even exists... :/
Hello? Is there anybody still reading this?
Ping. Same issue here, which means that .CSS files have to be version-controlled.
Same with .coffee files to .js files. Initially we just let VS check everything into git, then we got sick of merging JS files which should get regenerated anyway and removed them all. But then we have to go through and manually compile each of the files first. Not so bad if you just fire up the coffee command line compiler and tell it to compile all of the coffee in the solution folder, but it still seems pretty dumb to have to do so.
I just ran into this as well. It would be nice if it wasn't possible to crash VS during a build and just threw a build error instead. If I get a chance, I'll look at the code to see if I can do this.
In our project we use LESS and CSS minification, but we don't want to check the minified CSS files into Subversion since they are easily rebuilt during the build - or so we thought.
The problem is that when Web Essentials is configured to automatically compile LESS files on build, it'll then produce an exception if the minified CSS file doesn't already exist (see below) and a second or two later VS2012 crashes...
The exception is as follows:
Why would the LESS compiler ever need to read the existing minified file?
If all .min.css files exist (i.e. by opening the LESS file by hand and saving it again) the build finishes without problems and Visual Studio doesn't crash.