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 am having some painful cyclical issues with Web Workbench version 3.2.1035.22937. Let me elaborate... I have a file named _base.scss which is included by other files. So, let's say I have the following: _base.scss File1.scss File2.scss File3.scss If I modify _base.scss the other files get generated 3 times each. In reality I have 25 files and ruby.exe runs for several minutes generating each file 25 times. Furthermore, if I edit File2.scss then File1.scss and File3.scss also get compiled even though there are no dependencies between them. Am I misunderstanding something or do I possibly have something configured wrong? Thanks - Greg |
|
|
|
|
Try enabling the setting "Enable experimental fixes" under Tools/Options/Web Workbench to see if this improves performance.
|
|
|
|
|
I get the same behavior regardless of the "Enable experimental fixes" setting. |
|
|
|
|
Are you able to send us through a small project with a set of files which trigger this behaviour please and we can investigate this further for you and look to get this resolved. You can email these through to support at mindscape.co.nz or attach them to the forum post.
|
|
|
|
|
Jeremy, thanks again. I have sent a project file to the email address indicated that you can use to observe my issue. I referenced this thread in the email. Greg |
|
|
|
|
Jeremy, the email got bounced and I couldn't upload here because the full project was too large. I have zipped up just my sass folder, Img folder that my sass references, and my config.rb file. If you create an MVC 4 ASP.NET project in VS 2012 and drop these files in you should be good to go. To reproduce the issue do the following: 1) Open the project in VS 2012 2) Open the sass_base.sass file 3) Open the css\About.css file 4) Make a change to the _base.sass file. You should soon see a dialog telling you that About.css has been modified outside of the source editor. Click “Yes” to reload it. Shortly thereafter you will get the dialog again. Wash, rinse, repeat. The ruby.exe process will continue running for some time as it repeatedly generates the .css files over and over again. Greg |
|
|
|
|
Thanks for the repro Greg! Ive tracked this down and it was an issue when operating with the Compass compiler and picking up the appropriate dependencies. We have now added in a fix for this and this will be available in the next nightly build and will be included with the next gallery release.
|
|
|
|
|
Jeremy, that is good to hear and thanks for the quick turnaround. Good sleuthing. Greg |
|
|
|
|
We're just starting a sass/compass-based site redesign and have started trying to use Mindscape Web Workbench with Visual Studio 2013. We had noticed performance problems and then found this post. I have confirmed the same behavior of repeated updates to the output CSS file. So I, as the guinea pig, upgraded to the Pro version this morning and grabbed the current nightly build (Mindscape.WebWorkbench.Integration-20140128.10.vsix) and verified the installed plug-in version as 3.2.1163.23109. I've relaunched VS2013 and after forcing a SASS compile I still observe the repeated reloads of the output CSS file. I have experiment fixes enabled. Any thoughts on what else might be going wrong here? Thanks. -john |
|
|
|
|
No, although it does sound like the previous issue. Are you able to send us through a small repro project which highlights this and we can investigate whats going on.
|
|
|
|
|
Hi Jeremy, I created a minimal project containing only the sass and ruby config files. What I see here (and in the original project) is that the output css reloads happen only if there is an error in the sass (e.g. missing semicolon for an import statement). However, error or not, monitoring processes shows that a series of ruby process start and end for minutes after the css file is written (and the little "breathing" disk icon in the bottom status bar in Visual Studio shows activity for the duration.) One other item to note is that in VS, there doesn't seem to be any indication that there has been an error in the compilation. Anyhow, here are the details of my environment: OS: Windows 2007 Pro SP1 VS: Visual Studio Ultimate 2013 Version 12.0.21005.1 REL and Mindscape Web Workbench Version 3.2.1163.23109 In the meanwhile, we have disabled compilation through Web Workbench and have put in a post-build command to run a compass compile using a ruby/sass/compass installation which, in addition to completing quickly, also reports error status. Thanks, -john |
|
|
|
|
Hi John, Thanks for attaching the solution, unfortunately I haven't been able to repro this. In each VS2013 environment where Ive tried this the .css file is regenerated without issue and compilation doesn't take particularly long - probably about 2 seconds on average. Im a bit puzzled as well about your comment regarding multiple Ruby processes, again this would match the previous behaviour but not the current one. Are you able to try a nightly build?
|
|
|
|
