Using SASS in a team where not everyone has the Mindscape extension
I have a huge MVC project that I want to use SASS on. I cannot change my structure, so the solution I used is Mindscape.
Mindscape is great because it runs the SASS watcher behind the scenes and allows me to edit my SASS files by compiling it on the fly into my Styles directory (also: it comes with compass support).
The problem is that users who do not have these extensions have to manually install them as they are not part of the Nuget dependency manager. I have 2 questions:
- Is it possible to automatically install Mindscape on build as if it were a dependency?
- If this is not possible, what can I use to compile my SASS files when I save them so that the output goes to a different folder?
I've seen an extension for this, but this is for VS 2010, not 2012.
source to share
I was able to set up sass as part of a project in various ways, however, Compass, which gives SASS very powerful functionality, still requires an external ruby build.
Since we have various CI processes that need to work hand in hand, and since bringing the entire Compass library into a project sounds like overkill,
we will use Mindscape for a local developer and set up the SASS builder on our remote servers.
source to share
One approach is to prevent everyone from editing sass / css and keep it served by isolated front-end developers :)
The compiled css files can then be added to source control next to their sass source - so that every user can run the website locally with the latest stylesheets, and third-party developers can edit the source file, but they want to. It also eliminates the need for sass compilers on deployment servers, which can be attackers depending on the infrastructure's readiness to support such tools.
It's not an ideal way to deal with the problem, but compared to the overhead of having each one run locally, it's less than two evils. After initially setting up the protocol, this has been the case for us so far (big .NET dev store)
PS: I am considering switching to .less just because then everyone could use dotless with combres so that there are no third party tool dependencies. Lack of compass-like instrumentation is not for me, and your situation may be different.
source to share