Build completes with FAILED message, despite no visible Errors, but Detailed logging shows Task "EnableExtension" FAILED

[JogoShugh]

This is documentation of how I solved this:

I had a horrible time verifying whether the code in a fork by @lremedi (https://github.com/lremedi/VersionOne.Client.VisualStudio) could compile on my machine. The VSPackage project build said FAILED, but there were NO ERRORS, only a few warnings.

Here's how we resolved that:

• In Visual Studio 2012, I turned on Detailed MSBuild verbosity under TOOLS > Options > Projects and Solutions > Build and Run
• This showed the following output:

3>Task "EnableExtension"
3>Done executing task "EnableExtension" -- FAILED.
3>Done building target "DeployVsixExtensionFiles" in project "VersionOne.VisualStudio.VSPackage.csproj" -- > FAILED.

• With some googling, I found http://stackoverflow.com/questions/15747387/vsix-package-build-failed-without-showing-the-reason-visual-studio-bug,
• Sure enough under the Registry key HKEY_USERS\S-1-5-21-791890058-2983722243-1626712966-4341\Software\Microsoft\VisualStudio\11.0Exp\ExtensionManager\PendingDeletions I had entries for VersionOne Tracker.
• Deleted them!
• Rebuilt, then rebuilt and got this happy message:

========== Build: 3 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

[ibuchanan]

We can't really fix this ourselves. We have documented the problem in the README. Hence, we consider this issue resolved.

[mahee96]

Thanks for sharing this info, I was able to resolve one such issue by enabling detailed build log and output!!