Severity Code Description Project File Line Suppression State Error The "GetDeploymentPathFromVsixManifest" task failed unexpectedly. System.Runtime.InteropServices.COMException (0x80070005): ExternalSettingsManager::GetScopePaths failed to initialize PkgDefManager for C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv.exe 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 Microsoft.VsSDK.Build.Tasks.ExtensionManagerUtilities.GetSettingsManagerForDevenv(String rootSuffix) at Microsoft.VsSDK.Build.Tasks.GetDeploymentPathFromVsixManifest.Execute() at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext() MasterData
Hopefully someone else can get a better workaround. but for now this is what I got working:
This will let you resume working on the extension, but unfortunately you won't have any debugging support. and you will have to uninstall/install every time you want to test something.
This error appeared for me randomly without doing any change in the code. It disappeared after removing the following folders:
After it I am able to build again without error.
To find the folders I recommend to use some file search application and use the string "15.0_Exp*".
I noticed that my build errors were related to an XML Serialization issue. That made me think it was related to some messed up XML in the manifest, so...
source.extension.vsixmanifest file with a text editor. Make sure that there are no XML Errors. Use the Schema Reference to make sure everything is where it shoudl be.
My file had the
<Tag /> XML element nested in the
<Description /> XML Element which is not legal. I moved the
<Tag /> Element to the outside after looking at the
I got the same build error while trying to upgrade a VSIX package from VS 2015 to VS 2017. I was able to reproduce the same issue by creating a new empty VSIX project template and adding a new class via the Visual Studio Package template.
The VSIX project does not have any references by default, however, Visual Studio 2017 will automatically add references to all required Nuget packages when adding the Package class.
I was able to resolve the issue without unchecking the "Deploy VSIX content to experimental instance for debugging" option by downgrading the Nuget package for Microsoft.VSSDK.BuildTools from version 15.1.192 to version 15.0.26201.
I am using Visual Studio 2017 Enterprise version 15.3.0.
User contributions licensed under CC BY-SA 3.0