I just upgraded my VS 2017 to version 15.5.2, but get the following error dialog every time when open a VSTS project:
Error converting value "Microsoft.IdentityModel.Claims.ClaimsIdentity;xxxxxxxxxx\xxx#microsoft.com" to type 'Microsoft.VisualStudio.Services.Identity.IdentityDescriptor' Path 'authenticatedUser.descriptor', line 1, position 184.
What can I do to resolve this issue?
Found the root cause with the help from VS team.
An old version Microsoft.VisualStudio.Services.Common.dll was added into GAC which caused conflicts. This assembly should not be in GAC.
After removed this assembly from GAC, the annoying issue resolved.
Related
What to do to solve "The “GetDeploymentPathFromVsixManifest” task failed unexpectedly" when trying to debug a VS extension project??
Same question was already asked multiple times with different source reasons, all for VS2017 usually for upgrading VS extensions from VS2015, and it should have been solved with VS 2019. Yet, it just popped up.
The "GetDeploymentPathFromVsixManifest" task failed unexpectedly.
System.TypeLoadException: Method 'get_JoinableTaskFactory' in type 'Microsoft.VisualStudio.Sdk.BuildTasks.ExtensionEngineHost' from assembly 'Microsoft.VisualStudio.Sdk.BuildTasks.16.0, Version=16.9.2017.12405, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have an implementation.
at Microsoft.VisualStudio.Sdk.BuildTasks.ExtensionManagerUtilities.GetExtensionEngine(ISettingsManager manager, Boolean deletePendingUninstalls)
at Microsoft.VisualStudio.Sdk.BuildTasks.GetDeploymentPathFromVsixManifest.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
I have tried all the solution for the same error found on SO, so far to no avail. I am using VS 2019 Community 16.9.2, updated all packages, downgraded some to try, nothing really changes this error.
This is my first attempt on VSIX and I just downloaded an existing project from github and compiled it.
The github project is working (probably) since the extension is available on the marketplace.
Any other suggestions? Searches on this error in combination with the JoinableTaskFactory dont return exactly many results.
For me the solution was to do at least one of the following steps:
Delete the obj-folder in the project
Execute Reset the Visual Studio 2019 Experimental Instance. You can find this tool when you search it in the windows search bar.
Clean and Rebuild the project
Sometimes it helped if I did only one step and sometimes it only worked after doing all the steps.
I couldn't find out if there is a specific pattern behind, but doing all of the above steps always fixed the error for me.
Another issue where I got the same error was if there was the wrong external program selected under Project Properties -> Debug -> Start external Program. For VS2019 I need to select C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.exe
If I switched between Visual Studio Versions, then sometimes a different Visual Studio version was selected.
Uncheck: "Deploy VSIX content to experimental instance for debugging"
in solution properties->VSIX
Also Update installed NuGet packages.
I downloaded the Boilerplate template project today. I am able to build without errors and also create a database from the entity model. I have set 'Web.Mvc' project as the startup project.
When i run the application on VS Community 2019 16.4.4 i get the below error. What am i missing here?
Also, attach to process window does not open from Tools > Attach to process. I get the same error as in the image.
Error:
Unable to start debugging.
Operation not supported. Unknown error: 0x8ede000e
Build Error:
Resolved: I had to re-install VS Community 2019. The previous update corrupted VS2019. Installing V.16.5.4 fix the issue.
I have project which builds with no error but when I run code analysis on solution I get this Duplicate Identifier 'Promise' and Duplicate Identifier 'require' errors
My visual studio version is 2017 rc
I googled solution for this, found below link
https://github.com/Microsoft/TypeScript/issues/14565
Not getting any solution for this problem
I solved this issue by updating VS 2017 to version 15.2, I think it was bug in previous versions.
I have projects in a solution going from Visual Studio 2010 to Visual Studio 2015 with Update 1. I just installed VS2015 with update 1 on a Windows 7 Continuous Integration build server and I'm getting the following errors. I've been digging around on the Internet for a couple days now with no leads on how to fix this. I've read similar posts on here that relate to other "packages" not being loaded but the recommended fixes haven't worked for this. I've uninstalled and reinstalled vs2015 a few times and still get the same errors. Any thoughts or ideas on how to fix?
Package 'VisualBasicPackage' failed to load.
C:\Workspaces\AHLTA\Current\Product\Production\Shared\Security\Security.vbproj : error : The application for the project is not installed.
Package 'VisualBasicPackage' failed to load.
C:\Workspaces\AHLTA\Current\Product\Production\Shared\Shared\Shared.vbproj : error : Project 'Shared' could not be opened because the Visual Basic 2015 compiler could not be created. Please re-install Visual Studio.
Package 'CSharpPackage' failed to load.
C:\Workspaces\AHLTA\Current\Product\production\DataLayer\Dmdc\Immunizations.Messaging\Immunizations.Messaging.csproj : error : Project 'Immunizations.Messaging' could not be opened because the Visual C# 2015 compiler could not be created. Please re-install Visual Studio.
UPDATE #1: I think I may have resolved this myself just now.
I found this post and tried the suggestion, now the build seems to be compiling correctly with no errors.
vs2012 error: package 'visual c++ package' failed to load
The information on the following link seems to have solved the problem I'm having. http://happyivyli.blogspot.com/2013/07/visual-c-package-failed-to-load.html
I'm attempting to start using VS 2012 instead of VS 2010, but after installing VS 2012 and .Net 4.5. I'm getting code analysis errors in VS 2010 saying The following error was encountered while reading module 'xxx_Accessor': Could not resolve type reference: [System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089] System.Windows.Input.ICommand.
I'm guessing this is related to the fact that .Net 4.5 has moved the location of the ICommand interface, but is there a solution to this so that code analysis will run again? I've tried adding the ignorestrongassemblynames to the project file of the test project and the project under test, but that hasn't worked.
I've had just the same problem, but not with all of the assemblies that reference ICommands, just some.
I removed the reference to PresentationCore, rebuilt and re-added it. The problem went away.