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 was wondering if there's a way to prevent web workbench from generating a CSS file to accompany less files. In the free-edition it just generates an empty file that explains that css generation is a PRO feature. This causes a bit of a mess for my source-control. Also, sort of a bug report: If I delete the .css file (leaving the .less file intact). Sometimes when I open up the project again I get a duplicate entry for my less file. One with a css file and one without. Deleting one entry still deletes the .less file on the disc so the project gets a bit messed up from this. |
|
|
Update to the latest version, choose Mindscape > Web Workbench Settings, and uncheck the Compile box. |
|
|
Thank you for your quick response. I found the new settings page but I'm using the free edition it just has a flag with "Go Pro" under the compile heading and it's still trying to compile my LESS files into CSS producing the empty file that prompts me to use the pro edition if I want auto-compiling. |
|
|
Hmm, this is very strange. You are clearly using the latest version because you are seeing the settings page, but from searching the code that error message is no longer present in the code. One thing you could do is check if there is a custom tool associated with the .less file (Solution Explorer > right-click the .less file > Properties > Custom Tool option). If there is, delete that custom tool. Let us know if this was the problem -- the custom tools are no longer installed so this should be a "can't happen" bug, but perhaps somehow they have stuck around in the registry or something -- if that's the case we'd very much like to know about it so we can get it fixed for you! If there is no custom tool, or if deleting it doesn't help, could you delete the .css file, force a recompile, and post the contents of the spurious CSS file so we can try to track down which part of Web Workbench is generating the error message? Thanks! |
|
|
What I ended up doing was manually editing my .csproj file. I removed the Sub-Properties of the There's no custom tools attached to the files and prior deleting the CSS file only caused visual studio to make a duplicate entry when it re-loaded. It hasn't been a problem since I did the steps above. The following is the output of the Generated CSS:
|
|