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
|
I've had web workbench for a while now, and haven't did any work in sass for months and months. Today I tried to modify something and it breaks. This is in VS 2013. I dont have a compass project setup. I didnt even know it existed till looking through the threads today. lol i have a test.scss file and only thing in it is /* System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at Mindscape.VisualSass.Integration.CustomTool.ExternalCommandBase.Execute(String customToolFolder)
at Mindscape.VisualSass.Integration.Compilation.ScssCompiler.CompileCore(String scss, String sourceFilePath, String rootPath, IEnumerable Please help |
|
|
|
|
Try deleting the temp folder which resides at AppData\Local\Temp\Mindscape\WebWorkbench in your user folder (e.g. C:\Users\jeremy\AppData\Local\Temp\Mindscape\WebWorkbench) It sounds like the Ruby tooling is missing or corrupt, deleting the temp folder will cause it to be re-extracted. If that doesn't resolve the issue check that you don't have a custom Ruby path specified in the options under Tools/Options/Web Workbench
|
|
|
|
|
That worked. Thanks! |
|
|
|
|
Worked for me too. I am curious, as I just installed this package today. Following instructions I had also downloaded and installed Ruby. When I opened the Options panel I saw the place to put in the path to the Ruby files, which I figured I should do. Now it turns out that broke it. Why did that break it? Should I NOT have downloaded Ruby? Mike |
|
|
|
|
The fix described above covers where there has been some file corruption in the Ruby install we extract ourselves. You mention you were using a custom Ruby install though so this should have had no impact, Im guessing you removed the setting for your Ruby installation? Also when you specified your Ruby installation did you set the path to be the path for the bin folder or the base folder?
|
|
|
|
|
I downloaded Ruby and installed it as specified in steps 2 and 3 here. Everything looked good and then when I happened to be in the WW options I saw that placeholder for "path to Ruby" and I specified the base folder I had installed to, C:\Ruby22-x64. When I saw this post after having difficulty, the light bulb went on and I thought I should remove that path from there. Once I did that, WW worked fine. So my question was why having that path in there screwed it up? Perhaps it was wrong to go to the base folder? Secondly it also seems to indicate that, since it worked after I removed it entirely, perhaps WW itself is running Ruby under the covers? If so, then I didn't need to install Ruby separately at all, since I'm only interested in using tools that work within Visual Studio. I ask because as other team members come to maintain this project I want the setup instructions to be correct. -Mike |
|
|
|
|
Yes - you don't need to install Ruby separately as we maintain an internal Ruby distribution with Web Workbench.
|
|
|
|
