VSTO文档级自定义的仪表分析问题 [英] Problems with Instrumentation Profiling of VSTO Document Level Customisation

问题描述

我们开发了一个在Excel 2007中运行的VSTO应用程序.C＃部分非常慢，我们需要对其进行分析以提高速度。我们尝试使用Visual Studio的分析器使用检测分析来完成此操作。这导致了许多困难。
我们使用了以下步骤：

We have developed a VSTO application that runs in Excel 2007. The C# part was pretty slow, and we needed to profile it to improve the speed. We tried doing this with Visual Studio's profiler using instrumentation profiling. This resulted in numerous difficulties. We used the following steps:

1. 编译VSTO应用程序。
2. 延迟签署了申请。
3. 运行探查器。
4. 然后，探查器通过插入检测来修改我们的VSTO应用程序DLL。
   
5. 在批处理命令中，我们尝试仅使用公钥（使用sn.exe）重新签名DLL，但这不起作用。我们不得不用全密钥重新签名。 （在开发人员计算机上执行此操作显然会破坏代码签名证书的用途。）
   
6. Excel抱怨应用程序清单中的程序集引用不匹配。
   
7. 我们使用mage.exe更新了程序集清单，并使用完整的代码签名证书对清单进行了签名。
   
8. 然后看来应用程序清单和部署清单之间存在不匹配。
   
9. 我们使用mage.exe更新了部署清单，并使用完整的代码签名证书对清单进行了签名。我们使用-appm再次添加了应用程序清单。
   
10. 完成上述所有操作后，我原本期望VSTO应用程序运行。但它仍然抱怨不匹配。
    

1. Compile the VSTO application.
2. Delay signed the application.
3. Run the profiler.
4. The profiler then modified our VSTO application DLL by inserting instrumentation.
5. In a batch command, we tried to re-sign the DLL using only the public key (using sn.exe), but this did not work. We had to re-sign it with the full key. (Doing this on a developer machine obviously defeats the purpose of the code signing certificate.)
6. Excel complained about an assembly reference mismatch in the application manifest.
7. We updated the assembly manifest using mage.exe, and signed the manifest with the full code signing certificate.
8. It then appeared that there was a mismatch between the application manifest and the deployment manifest.
9. We updated the deployment manifest using mage.exe, and signed the manifest with the full code signing certificate. We added the application manifest again using -appm.
10. After all the above I would have expected the VSTO application to run. But it still complains about mismatches.

仪器分析VSTO应用程序时应遵循哪些适当的步骤？

What are the appropriate steps to follow when instrument profiling a VSTO application?

是否可以重新使用部分签名签署延迟签名程序集（仅限公钥）？如果是这样，我们应该怎么做？如果没有，如何合理地执行上述开发方案？

Is it possible to re-sign a delay signed assembly using partial signing (public key only)? If so, how should we do it? If not, how can one sensibly execute the development scenario described above?

我们最终下载了Redgate ANTS Performance Profiler的演示版本。这很快就能轻松完成。我不想买它，因为我已经支付了Visual Studio。

We ended up downloading a demo version of Redgate ANTS Performance Profiler. This works quickly and easily. I don't want to buy it, though, since I already paid for Visual Studio.

谢谢

Johan

推荐答案

嗨约翰，

重新签署VSTO清单，请参阅博客
http://blogs.msdn.com/b/vsto/archive/2009/04/29/signing-and-re-signing-manifests-in-clickonce.aspx 其中描述了重新签署清单的步骤。

For re-signing the VSTO Manifest, please refer to blog http://blogs.msdn.com/b/vsto/archive/2009/04/29/signing-and-re-signing-manifests-in-clickonce.aspx which describes steps to re-sign manifests.

没有关于分析VSTO文档级自定义的具体建议。您可以通过发布.Net Windows应用程序（单击一次）重新创建相同的方案。请在
上发布与分析相关的问题
http ：//social.msdn.microsoft.com/Forums/en-US/vstsprofiler/threads 。

There are no specific recommendations for profiling VSTO document level customization. You can re-create the same scenario by publishing .Net windows application (click-once). Please post the questions related to Profiling on http://social.msdn.microsoft.com/Forums/en-US/vstsprofiler/threads.

谢谢，

  ;

 

这篇关于VSTO文档级自定义的仪表分析问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！