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 getting an error installing a nightly build of Web Workbench in VS2010. It installs fine in VS 2011, but I get an error in the MS VSIX Installer. When I click on debug, I get a DirectoryNotFoundException. Could not find a part of the path 'C:\USERS\JAY\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\10.0\EXTENSIONS\MINDSCAPE\MINDSCAPE WEB WORKBENCH\3.0.38.19767\extension.vsixmanifest'. I added that directory and copied an installation there to get through this issue, but I am not sure why it happened. |
|
|
Does this happen on any nightly build (or just that one)? Are you running Visual Studio 2010 as an admin or non admin and if non admin does running it as an admin change the behavior?
|
|
|
I started getting this error about a month ago. I just grabbed the latest nightly and I'm getting "The Mindscape.VisualSass.Integration.VisualSassPackage, Mindscape.Webworkbench.Integration.10, Version=3.2.245.20464... did not load correctly" (forgive typos, you can't copy/paste). It refers me to an ActivityLog.xml file that does not exist. Once in this state (it happened before) I have to manually find and delete folders with random-names under %LOCALAPPDATA%\Microsoft\VisualStudio\10.0\Extensions Otherwise "uninstall" inside VS simply disables the plugin and the installer thinks it's still there. Are you supposed to be running VS when you click the .vsix? |
|
|
No you should be able to run the VSIX just by double clicking on it regardless of if Visual Studio is loaded, but we have heard of issues with it updating packages if this is not done from within Visual Studio. The random-name thing seems to occur when you install the VSIX from the command line rather than via the Visual Studio Extension Manager - again not sure why that is as it should be installing to a Company\Product\Version folder as defined in the manifest but this just seems to be one of those VSIX wrinkles.
|
|