无法调试VSIX项目 [英] Unable to debug VSIX project

查看:1021
本文介绍了无法调试VSIX项目的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图开发我的第一个视觉工作室扩展项目,我安装了VS10 SDK,并且能够创建一个新的项目,并且可以构建它,但是当我尝试调试符号没有加载。我知道我可以调试到VSIX项目,因为我已经在线下载了一个示例项目,它的符号被加载,并且断点被罚款 http://weshackett.com/2009/11/configure-vsix-project-to-enable-debugging/ )。
所以一定是与创建VSIX项目的方式有关(也许!)。
我注意到的一件事是,dll和文件没有被复制到本地的应用程序数据区域,只有清单被复制,而对于示例项目,所有文件都被复制包括dll。我比较了两者之间的项目设置,它们都是一样的。
我希望它是有道理的,如果我可以提供更多的细节,然后让我知道...

解决方案

我设法让它工作。为了这样做,我不得不卸载vsix项目并将文件编辑为xl文档。



从项目文件中删除以下行:

  ; IncludeAssemblyInVSIXContainer> 
false
< / IncludeAssemblyInVSIXContainer>
< IncludeDebugSymbolsInVSIXContainer>
false
< / IncludeDebugSymbolsInVSIXContainer>
< IncludeDebugSymbolsInLocalVSIXDeployment>
false
< / IncludeDebugSymbolsInLocalVSIXDeployment>
< CopyBuildOutputToOutputDirectory>
false
< / CopyBuildOutputToOutputDirectory>
< CopyOutputSymbolsToOutputDirectory>
false
< / CopyOutputSymbolsToOutputDirectory>

或将其设置为true:

 < IncludeAssemblyInVSIXContainer> 
true
< / IncludeAssemblyInVSIXContainer>
< IncludeDebugSymbolsInVSIXContainer>
true
< / IncludeDebugSymbolsInVSIXContainer>
< IncludeDebugSymbolsInLocalVSIXDeployment>
true
< / IncludeDebugSymbolsInLocalVSIXDeployment>
< CopyBuildOutputToOutputDirectory>
true
< / CopyBuildOutputToOutputDirectory>
< CopyOutputSymbolsToOutputDirectory>
true
< / CopyOutputSymbolsToOutputDirectory>

或将它们添加到...节点下,如果它们不存在。



一旦我删除了这些行并重建了解决方案,dll和pdb现在被复制到bin\debug文件夹以及AppData\Local\Microsoft\\ \\ VisualStudio\10.0Exp\Extensions\文件夹。


I'm trying to develop my first visual studio extensions project, I have VS10 SDK installed and was able to create a new project and can build it fine, however when I attempt to debug symbols are not loaded. I know that I can debug to VSIX project since I have downloaded a sample project online and it symbols are loaded and break points are being hit fine http://weshackett.com/2009/11/configure-vsix-project-to-enable-debugging/). So must be something specifically to do with the way I have created the VSIX project ( maybe !). One thing I do notice is that the dll and files aren't being copied over to the local "Application Data" area, only the manifest is being copied over, while for the sample project, all files are being copied over including the dll. I have compared project settings between both and they are both the same. I hope it makes sense, if I can provide any more detail then let me know...

解决方案

OK I managed to get it working. In order to do so, I had to unload the vsix project and edit the file as an xl document.

Either remove the following lines from the project file:

<IncludeAssemblyInVSIXContainer>
    false
</IncludeAssemblyInVSIXContainer>
<IncludeDebugSymbolsInVSIXContainer>
    false
</IncludeDebugSymbolsInVSIXContainer>
<IncludeDebugSymbolsInLocalVSIXDeployment>
    false
</IncludeDebugSymbolsInLocalVSIXDeployment>
<CopyBuildOutputToOutputDirectory>
    false
</CopyBuildOutputToOutputDirectory>
<CopyOutputSymbolsToOutputDirectory>
    false
</CopyOutputSymbolsToOutputDirectory>

or set them to true:

<IncludeAssemblyInVSIXContainer>
    true
</IncludeAssemblyInVSIXContainer>
<IncludeDebugSymbolsInVSIXContainer>
    true
</IncludeDebugSymbolsInVSIXContainer>
<IncludeDebugSymbolsInLocalVSIXDeployment>
    true
</IncludeDebugSymbolsInLocalVSIXDeployment>
<CopyBuildOutputToOutputDirectory>
    true
</CopyBuildOutputToOutputDirectory>
<CopyOutputSymbolsToOutputDirectory>
    true
</CopyOutputSymbolsToOutputDirectory>

or add them under the ... node if they don't exist.

Once I removed these lines and rebuilt the solution, the dll and pdb were copied now as expected to the bin\debug folder as well as to the "AppData\Local\Microsoft\VisualStudio\10.0Exp\Extensions\" folder.

这篇关于无法调试VSIX项目的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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