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
|
This is the best contribution to visual studio since intellisence :DThe first thing i've tried is to create a hierarchy of scss files with imports. lets say i have base.scss and frontpage.scss, frontpage file imports base file and it work perfectly when saving frontpage.scss it will generate the contents of base and frontpage. This is how css should have been made in the first place!!
The problem is when you make a change to the base file, it doesn't trigger generation on the files that are importing the base. Thus you need to manually right click on the .scss file and click run custom tool. Is there any way to run ScssGenerator custom tool for all of the scss files in the project? |
|
|
|
|
Thanks for the kind words! Unfortunately, because of the way we are integrating into Visual Studio, it's not currently possible for us to recompile dependent files when an included file changes. We're aware of this limitation and it's something we want to address, but we'll need to build a bit more infrastructure before we can do it. There isn't a built-in way to run a custom tool across a project as far as I know, but you could probably put together a Visual Studio macro that does it. Try using the VS macro recorder to get a script for doing a Run Custom Tool on a single file in Solution Explorer, then if that works you should be able to put some code around it to traverse the project and apply the same action to every .scss file. You might even be able to hook it up so that it runs whenever you save a .scss file, though this could be a bit inefficient if you have a lot of files and like to do lots of incremental saves! http://msdn.microsoft.com/en-us/library/ms228948.aspx would be a good place to start (though you will need DocumentEvents rather than EnvironmentEvents to get the Saved event). If you do either of these and are able to get them working, we'd love it if you'd be willing to share them with other users. If you don't have any joy with the macro approach, though, let us know and we'll see what we can do. |
|
|
|
|
I have the same problem. My company would like to use Sass and thus Web Worbench, but the lack of automatic dependent file compilation makes it practically impossible for us. Do you have this feature on a roadmap for the near future? Thanks for the great product anyway! |
|
|
|
