0

My question is in big environment preferably would like to lockdown people from editing the generated CSS files instead of in our case .scss files.

Highly recommend anyone who is using Visual Studio for front end development to check out Web Workbench plugin, that allows you to takeadvantage of precompiling CSS with SASS/LESS and javascript with CoffeeScript. You will need to install IronRuby but both are very easy installs.

PDA
  • 766
  • 6
  • 10
  • 2
    If your .css files are generated, then you should consider not checking them in. You don't check in .exe files, do you? – John Saunders Apr 19 '12 at 20:50

1 Answers1

1

You can accomplish this through the Check-in policies that come with the Team Foundation Server Power Tools. There's a forbiddenpattern policy that will prevent checking in files that match a specific pattern.

If needed, you can combine this with the Custom path policy to scope these blocked patterns to specific locations (so that you can check in the compiled result into certain folders, but not just anywhere)

You can overrule either rule, if you want, but need to provide a reason comment for that. These overrides can be monitored.

More information on Check in policies.

jessehouwing
  • 106,458
  • 22
  • 256
  • 341