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
|
When running 'Run Custom tool' I've got the following error: "The custom tool 'ScssGenerator' failed. Could not find a part of the path 'C:\Users\$$$$$\AddData\Local\assembly\dl3\A7Z19ADX.LJM\QGG3OXL4.O4M\8a518f65\b58ac979_ac48cc01\CustomTool\Sass.zip'" |
|
|
|
|
Hmm, something very strange in the user profile there. Your Visual Studio extensions should be installing and running from [username]\AppData\Local\Microsoft\VisualStudio\10.0\Extensions. Can you take a look in that directory and let us know whether it contains a Mindscape\Mindscape Web Workbench subfolder? If so, as a workaround you may be able to get away with copying the CustomTool folder from the "proper" install directory to the weird folder that it claims to be running from. Not sure why it is running from that folder though... |
|
|
|
|
Yes, I've have the same issue. It seemed to have occured after a reboot. I do have the workbench installed in the correct directory and can find the Sass.zip file in ... C:\Users\*\AppData\Local\Microsoft\VisualStudio\10.0\Extensions\Mindscape\Mindscape Web Workbench\1.0.161.18005\CustomTool I installed the extension via visual studio Extension Manager, but will try the vsix installer, not sure if it will make a difference |
|
|
|
|
Yea, I downloaded the .vsix installer, ran it, and then restarted Visual Studio. All good now. |
|
|
|
|
Thanks for the extra info. We've tried installing from the VS Gallery and rebooting, but haven't been able to reproduce the problem. We're a bit stumped as to what's going on here (glad to see you have a workaround, but we'd still be happier if we could track down the cause!). I'm wondering if there's some special configuration option relating to shadow copying of DLLs or something. I can find a bunch of DLLs, both referenced DLLs and extensions, in those funny-looking directories, but no clue as to why they're there. What other extensions and add-ons do you guys have installed in VS2010? |
|
|
|
|
I'm running VS2010 Ultimate v10.0.40219.1 SP1 Rel with extensions : AnkhSVN v2.1.10129.17 NuGet Package Manager 1.2.20325.9034 Resharper 5.1.3000.12
Good luck! |
|
|
|
|
Hmmm, nope I'm getting this error again :( ... "The custom tool 'ScssGenerator' failed. Could not find a part of the path. the only work around I have at the moment is to reinstall from .vsix
|
|
|
|
|
Was this again after a reboot? If so, do you have time to try it again, reinstalling and then deliberately rebooting to see if it breaks? We haven't been able to reproduce this issue which is always half the battle...! I'll also try making a few tweaks so we can see if that helps -- will let you know when these are available. Thanks for your patience and your help in identifying the problem! |
|
|
|
|
actually, didn't have to reboot the os, i just rebooted visual studio. when I opened the .scss file I saw the associated .css file, then made a change to the .scss file and saved it, the .css disapeared. Then when I 'run Custom Tool' I get the error.
|
|
|
|
|
The issue repeats EVERY day after starting the OS. I guess this is the same as "after reboot". |
|
|
|
|
I'm afraid we are absolutely stumped as to what is causing this. However, we have updated the extension so it will now try to detect and recover from this issue. Because we are not sure what the cause is, we can't absolutely guarantee this will fix it for you, but based on the info we have, we think it should. Please check the Updates tab in Extension Manager (it may take a minute or so to appear) and try installing the latest version (build 18114). It should be okay to do this from Extension Manager rather than by downloading the VSIX -- though, as I say, we cannot be 100% sure about anything to do with this issue...! We realise this problem is very frustrating and we appreciate your patience on this. Do let us know whether the update fixes the problem. |
|
|
|
|
Thanks!! It seems that latest build fixed the issue. |
|
|
|
|
Replying to the last question "What other extensions and add-ons do you guys have installed in VS2010?"
Just to give you guys some more feedback...
|
|
|
|
