Compilation error when saving SCSS file

Hi!

When working with a scss file I get this error in the generated .css file every time.

Parameter name: codepage
   at System.Text.Encoding.GetEncoding(Int32 codepage)
   at ICSharpCode.SharpZipLib.Zip.ZipConstants.ConvertToString(Byte[] data, Int32 count)
   at ICSharpCode.SharpZipLib.Zip.ZipConstants.ConvertToStringExt(Int32 flags, Byte[] data)
   at ICSharpCode.SharpZipLib.Zip.ZipInputStream.GetNextEntry()
   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`1 additionalPaths, ICompilationSettings settings, ICompilerContext context, CompilationResult result)
   at Mindscape.VisualSass.Integration.Compilation.CompilerWithMinification.Compile(String text, String sourceFilePath, String rootPath, IEnumerable`1 additionalPaths, ICompilationSettings settings, ICompilerContext context, CompilationResult result) */

Any ideas why this happens?

No Im afraid not, but are you using a foreign language version of Windows? If so do you know what codepage you are using?

As a workaround you can extract the Ruby193 zip file which you can find under %APPDATA%..\Local\Microsoft\VisualStudio\11.0\Extensions[some random name]\CustomTool to an appropriate location on your system and then set the Ruby Installation Path option which can be found under Tools/Options/Web Workbench in the Compilation section to be the bin folder path from the files you extracted.

e.g. If I extracted that zip file to C:\Temp\WWRuby then my Ruby Installation Path would need to be set to C:\Temp\WWRuby\Ruby193\bin

If you are using Visual Studio 2010 replace 11.0 with 10.0 in the earlier path above.

This will remove the need for us to extract this and should remove the issue from appearing.

Jeremy

Thanks. This finally worked for me!