VSIX软件包生成失败,但未显示原因(Visual Studio错误) [英] VSIX package build failed without showing the reason (Visual Studio bug)

查看:383
本文介绍了VSIX软件包生成失败,但未显示原因(Visual Studio错误)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我必须启用MSBuild项目构建输出详细信息的诊断模式才能看到此信息:

I have to enabled diagnostic mode of MSBuild project build output verbosity to see this:

1>Done executing task "EnableExtension" -- FAILED. (TaskId:81)
1>Done building target "DeployVsixExtensionFiles" in project "myextension.csproj" -- FAILED.: (TargetId:93)
...
1>Build FAILED.
1>
1>Time Elapsed 00:00:01.27
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

我的问题是我无法调试正在使用的Visual Studio扩展包,因为生成输出显示某些故障.有线连接已创建,其中包含所有内容(包括vsix软件包)的obj和bin文件夹.我真的不知道我做了什么特别的更改,因为几个小时前一切都很好.

My problem is I cannot debug the Visual Studio extension package I'm working on, as the build output says something has failed. What's wired, the obj and bin folders with all content inside (including vsix package), has been created. I don't really know what special I've changed, because few hours ago everything was fine.

我如何调查出了什么问题?

How can I investigate what has gone wrong ?

顺便说一句:我正在使用VS 2012 Premium Update 1

Btw: I'm using VS 2012 Premium Update 1

我记得自己做了什么.在调试模式下,我进入工具->扩展和更新,并卸载了当前调试的扩展(在执行此操作后无需重新启动VS).进一步尝试调试(在VS实验实例关闭后F5)会导致这种神秘的生成行为.

I remembered what I've done. While being in debug mode, I entered Tools -> Extensions and Updates, and uninstalled my currently debugged extension (without restarting VS after that operation). Further attempt of debugging (F5 after CLOSING Experimental Instance of VS) results in this mysterious build behavior.

推荐答案

一段时间后,我目前想出的解决方法是更改​​ source.extension.vsixmanifest <中的扩展包的显示名称./strong>文件:

My current workaround I've come up with after some time is to change the display name of the extension package in the source.extension.vsixmanifest file:

  <Metadata>
    ...
    <DisplayName>Change this name to sth else and press F5</DisplayName>
    ...
  </Metadata>

无需进行其他任何更改(不幸的是,还原为旧名称仍会引发此错误,但至少可以继续进行开发和调试).

Nothing else needs to be changed (unfortunately reversion to old name still fires this error, but at least developing and debugging can be continued).

更新:

我已经在Windows注册表中检查了此类有问题的名称,并找到了以下PendingDeletions键:

I've checked the windows registry for such problematic name, and found following PendingDeletions key:

HKEY_USERS\S-1-5-21-1832937852-2116575123-337272265-599953\Software\Microsoft\VisualStudio\11.0Exp\ExtensionManager\PendingDeletions

在此键下,有一个值指向我以前卸载的扩展名(处于调试模式时):

Under this key there is value pointing at my extension I've previously uninstalled (while being in the debug mode):

C:\USERS\G_159\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\11.0EXP\EXTENSIONS\JAROSLAW WALISZKO\MYEXTENSION\1.0\

删除此条目可解决此问题.

Removal of this entry fixes that case.

这篇关于VSIX软件包生成失败,但未显示原因(Visual Studio错误)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆