Compass alternative css output directory and Source Control

Hi,

We have been using WW for about 18 months now and love it. We have recently started exploring the Compass features in an effort to reduce our SCSS duplication. However we have come across a problem when saving changes to our scss files.

We have specified an alternative output path for the CSS by setting the css_dir property in the config.rb file;

css_dir = "/Content/Css"

It all works perfectly. However, when the target css file is checked in to our source control (TFS) and we edit a source scss file, the target file does not automatically get checked out and we see an error in the Web Workbench Output

Errno::EACCES on line ["56"] of C: Permission denied - D:/OMG.Pact/OMG.Pact.www/Content/Css/main.css Run with --trace to see the full backtrace

I appreciate we can manually check these files out, but this would most likely prevent adoption of compass with our developers. Is there any way around this?

We added some changes recently which should cover this type of problem. Check to see if you have an option called "Force Compass Stylesheets to be writable" in Tools/Options/Web Workbench under the Compass section. If you see this set it to true and see if that resolves the problem for you. If you don't see this option you will want to update to the current nightly build.

Jeremy

Hi,

Unfortunately, this doesn't solve the problem. I can see the option in Tools > Options > Web Workbench and have set it to true. However, I still get the same error message.

If it helps, I am running Web Workbench 3.2.972.22809. My project structure is as follows;

/sass (contains the scss files)

/Content/Css (contains the css files Web Workbench is trying to write to)

config.rb contains the following;

http_path = "/"
css_dir = "/Content/Css"
sass_dir = "sass"
images_dir = "images"
javascripts_dir = "javascripts"

It's not a massive problem, but would really easy our use of WW if this could be resolved. Many thanks.

Try running Visual Studio with administrator privileges and see if this resolves the issue.

Jeremy

I was already running VS as Administrator, when I got the error message. Double checked to make sure this was the case, but no dice!