We are currently evaluating EPiServer and are having a bit of trouble near the first hurdle of installing the Visual Studio extension. Every time we do, we end up with an error, below is the log file that explains the error. Any help getting this installed would be appreciated.
Thank you for your responses in advanced
03/07/2013 14:27:09 - Microsoft VSIX Installer03/07/2013 14:27:09 - -------------------------------------------03/07/2013 14:27:09 - Initializing Install...03/07/2013 14:27:10 - Extension Details...03/07/2013 14:27:10 - Identifier : EPiServer.CMS.B7A45E5E-3836-4864-A117-95207E71A9B303/07/2013 14:27:10 - Name : EPiServer CMS Visual Studio Extension03/07/2013 14:27:10 - Author : EPiServer03/07/2013 14:27:10 - Version : 7.0.582.203/07/2013 14:27:10 - Description : EPiServer CMS extensions to Visual Studio03/07/2013 14:27:10 - Locale : en-US03/07/2013 14:27:10 - MoreInfoURL : http://visualstudiogallery.msdn.microsoft.com/4ad95160-e72f-4355-b53e-0994d2958d3e03/07/2013 14:27:10 - InstalledByMSI : False03/07/2013 14:27:10 - SupportedFrameworkVersionRange : 4.003/07/2013 14:27:10 - 03/07/2013 14:27:10 - Supported Products : 03/07/2013 14:27:10 - Microsoft.VisualStudio.Pro03/07/2013 14:27:10 - Version : [10.0]03/07/2013 14:27:10 - Microsoft.VisualStudio.Pro03/07/2013 14:27:10 - Version : [11.0]03/07/2013 14:27:10 - 03/07/2013 14:27:10 - References : 03/07/2013 14:27:10 - 03/07/2013 14:27:10 - System.IO.DirectoryNotFoundException: The system cannot find the path specified. (Exception from HRESULT: 0x80070003) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.VisualStudio.Settings.ExternalSettingsManager.GetScopePaths(String applicationPath, String suffixOrName, String vsVersion, Boolean isLogged, Boolean isForIsolatedApplication) at Microsoft.VisualStudio.Settings.ExternalSettingsManager.CreateForApplication(String applicationPath) at VSIXInstaller.App.GetExtensionManager(SupportedVSSKU sku) at VSIXInstaller.App.GetExtensionManagerForApplicableSKU(SupportedVSSKU supportedSKU, IInstallableExtension installableExtension, List`1 applicableSKUs) at VSIXInstaller.App.InitializeInstall() at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute()
Ok, in case this helps anybody out there, I now have a partial solution.
The problem seems to occur if your Windows setup has 'My Documents' at a different location other than the default, in our case it is a network drive. The problems come in that the VSIX installer does not work when this is at a location other than the default and by searching on the web, there appears to be no fix.
The solution for us looked to be to get into the registry, change the locations where this had been set and then try the install. These locations had to be set back afterwards for IIS Express to work because it wouldn't with the new settings. I also haven't closed Visual studio or shut down my machine because I do not want to break it!
To change the registry settings go to start > run... > type 'regedit' and hit 'ok'
Then browse to the following locations:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\PersonalHKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\ Personal
and set the keys to C:\Users\*your username*\Documents, where *Your username* is your actual username.
Then you should be able to install extensions such as the EpiServer visual studio extension.
why do you use your documents folder on a shared server? that seems strange in a dev.envrionemnt speciellay since many programs like VS use that folder to store information about templates and integrations other then episerver as well.
I couldn't agree more! Unfortunately it's the setup of everybodies machines in the organisation by IT, because it allows them to have everybody standardised and allow things like backups of our work on the server.
We've not had too many problems in the past with this setup, visual studio has handled it pretty well, but are running into problems now which will hopefully help instigate a change later on when move to new machines.