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 uninstalled and re-installed Web Workbench, tried rebooting my machine, etc. Any idea what's going on or how to troubleshoot this? /* System.IO.IOException: The process cannot access the file 'C:\Users\Dylan\AppData\Local\Temp\Mindscape\WebWorkbench\Ruby193\Ruby193\bin\libeay32-1.0.0-msvcrt.dll' because it is being used by another process.
at System.IO._Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITYATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
at Mindscape.VisualSass.Integration.ZipFileUtils.Unzip(String path, String directory)
at Mindscape.VisualSass.Integration.CustomTool.RubyCommand.Initialize(String customToolFolder)
at Mindscape.VisualSass.Integration.CustomTool.ExternalCommandBase.Execute(String customToolFolder)
at Mindscape.VisualSass.Integration.Compilation.ScssCompiler.CompileCore(String scss, String sourceFilePath, String rootPath, IEnumerable |
|
|
Feeling a bit dumb, but I believe I've resolved the issue. I had compile options as follows: //* scss-compile-options: --watch sass:public Removing this resolved the issue and allowed my sass files to compile. Just to provide a bit of context, my reason for setting this compile option was because I wanted changes I made to my application source files in Chrome to save and get reflected in my external text editor. I recently had success with automatically reloading my .scss file changes to the browser, and was hoping to achieve a similar behavior going the other way, i.e. sending changes made in chrome "sources" back to Visual Studio. Anyway... apparently this was not the correct way of doing so. |
|