Highlighted syntax in the SASS files I was looking at, which is why it's not 1 star. However it added a nag-ware popup hiding a nontrivial percentage of the syntax-highlighted sass, kind of defeating the purpose. Inserted nags into build output. Broke intellisense in cshtml files. Overall, a net loss in productivity; I uninstalled.
I wish I had read these reviews before purchasing the pro version.
Trying to use it with Foundation 5 for sites... no documentation on where or how to set compilation path... as in nuget instructions Open up the Web Workbench Settings for your project (select the project and use the right click context menu, or the Mindscape menu) you can set the Output Folder for your SCSS file and specify where the .css and/or .min.css will be generated.
Lacks help files... or doc for common tasks like this one should be. Waste of $.
Using the free version, if I go to Settings under Mindscape menu in my Visual Studio 2013, and select an Output folder for my .less file, it still has "..." as the Output folder for that .less file. It's like it didn't update. When I edit my .less file, my corresponding .css file did not update.
I definitely understand the "minify" option being available only via pro, but, please at least get the .less->.css working. Thanks!
the free Version does not compile less to css, so what's so cool with it, the splitted window without functionality or the begging for Money bubble? what does the paid Version? remove the bubble? Please don't fool me, that's less than useless.
This is a good extension but once my sass files get a little more complicated I have to wait 3 seconds or more between typing characters. It is unusable when this happens. I would give this extension 5 stars but the fact that I can't even type my sass out without waiting a million years makes it incredibly frustrating to use.
It is possible to import directory with /* syntax. I have purchase Webbench, and I am having problems using the /* syntax for all files. Can anyone explain what I am doing wrong. I currently list the 50 or so sass files individually.
Recently I upgraded from Visual Studio 2012 to 2015. I'm getting odd behavior from the 2015 Web Workbench CoffeeScript compiler. In certain cases tabs within the CoffeeScript are not recognized and in others properties within a class' constructor are compiling into functions. This does not happen in Visual Studio 2012. I can provide example code if need be. Is there any known issues? Does the Pro version have these problems too?
We are moving to Visual Studio 2015 and it is my understanding that Mindscape will not work in 2015 at this point. I've seen nothing to indicate when it a version actually officially supported will be released.
I use the Pro version since long time, only for coffeescript. I'm happy about this tool, works for coffeescript very cool! But an error came with VS 2015: The settings will be forgotten at every start of VS. So I must tell every day the pathes for *.js, and thats no fine work! Please repair this, please :)
I am using this great extension but facing a problem while using it. I created a SCSS folder and a CSS Folder under styles directory. I have given output directory to be the CSS folder. When I save the the scss file it generates the file in SCSS folder and CSS folder as well. Can anybody help me with this.
How do i get sass files to update themselves in visual studio with mindscape workbench? Every time a change is made to a sass file visual studio prompts to reload the file. I want this to be done automatically so I dont have to be click 'yes to all' ever time I make changes to the sass file.
As part of a team of front end developers working in a larger group we are using Web Workbench to maintain our scss files.
Does the Pro version allow us to automate the generation of the built css files as part of the build process?
Basically, we want to remove the generated css files from the version control and have it that ALL teams members generate the latest css on build.
This can't be done - Microsoft deliberately blocks extensions in the Express versions of Visual Studio so it's outside our control. HOWEVER, Microsoft recently announced the new Visual Studio Community 2013 Edition. This is also free but does support extensions. You'll want to move to that to be able to use Web Workbench.
I hope that helps,