This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I'm getting this with the latest update of LESS. The generator doesn't run. |
|
|
|
|
What is the build number of your version of Web Workbench? (The last bit of the version number shown in Extension Manager: it should be a five-digit number.) |
|
|
|
|
We switched from a custom tool based compiler to a background compiler in Web Workbench 3.0. Web Workbench will remove the custom tool settings as it recompiles each file. You can safely ignore this warning. |
|
|
|
|
Um, you seem to have edited away your original post. Does this mean the Less 1.3 / Twitter Bootstrap issue is now fixed? |
|
|
|
|
I'm running version 3.1.140.20147 for Visual Studio 2010 SP1. Edit: yes, i did change the post. For some reason i wasn't seeing updates in Extension Manager. So i thought the extension was up to date, which it wasn't. I ended up uninstalling and installing. Now I get this. |
|
|
|
|
I'm a bit confused. It's not generating CSS from less files. Both minified and debug files are empty. I tried building the project hoping it would generate, but they're all empty. |
|
|
|
|
Open the .less file you want to compile, make a change (such as adding a space or blank line) and save the .less file. You should now see CSS output (it may take a couple of seconds because Web Workbench is now doing the compile in the background). If you don't see anything, check the Mindscape > Web Workbench Settings window to make sure that compilation and minification are turned on for this file (they should be by default for .less files), and try opening the Output window and then recompiling to see if any messages appear. |
|
|
|
|
Gotcha. It's running on save event. I used to run the older version from the custom tool hence the confusion. Sorry for the stupid question. It's working now. Thanks for help! |
|
|
|
