使用ilasm失败，但没有给出原因 [英] Failure using ilasm, but no reason given

问题描述

我正在尝试使用 ILASM ，并且该过程似乎中止并显示以下消息:

  *****失败***** 

如何找出失败的原因?我可以打开详细消息还是可以查看日志文件?

解决方案

虽然我意识到现在为时已晚，无法帮助问题作者，但我将在此处保留这些详细信息，以防将来对某人有所帮助.>

最近我遇到了类似的问题，其中 Ildasm 使我能够将某些DLL分解为IL，但是 Ilasm 将 not 让我重新组装它们到DLL中.像问题作者一样，我的控制台输出非常无用，只是说:

  *****失败***** 

但没有列出任何原因.

就我而言，这是一个简单的错误，其中我将我的强名称密钥文件复制到了错误的目录中.在意识到并将其放置在正确的位置后， Ilasm 可以成功访问它，因此能够重新组装我的DLL.

我很遗憾在错误输出中没有提到这个基本错误...这是我认为出错的第一件事...或者也许就是为什么没有列出...是因为它很容易修复?

---

更新>>>

一种判断是否存在此确切问题的方法是查看控制台窗口的输出...没有有效的强名称密钥文件， Ilasm 会在末尾停止 Assembled method ... 部分，例如每行行上都将包含以下(或类似内容):

 组合的方法Namespace.SubNamespace.ClassName :: MethodName 

如果输出中包含以下几行，则可能与此问题不同，因为在没有强名称密钥文件的情况下，输出中应缺少该问题:

 创建PE文件发射类: 

I am trying to use ILASM and the process seems to abort with the following message:

***** FAILURE *****

How can I find out why it has failed? Can I turn on verbose messages or is there a log file I can look at?

解决方案

While I realise that this is probably too late to help the question author now, I will leave these details here in case it helps someone in the future.

I had a similar problem recently where Ildasm would enable me to disassemble some DLLs to ILs, but Ilasm would not let me reassemble them into DLLs. Like the question author, my console output was very unhelpful, just stating:

***** FAILURE *****

But without any reasons listed.

In my case, it was a simple error, where I had copied my Strong Name Key file into the wrong directory. After I realised and put it into the correct location, Ilasm could access it successfully and was therefore able to reassemble my DLLs.

I think that it is a real shame that this basic error wasn't mentioned in an error output... it's one of the first things that I could think had gone wrong... or maybe that's why it wasn't listed... because it was easily fixed?

---

UPDATE >>>

One way that you can tell if you have this exact problem or not, is to look at the Console Window output... with no valid Strong Name Key file, Ilasm stops at the end of the Assembled method ... section, eg. every line will have the following (or similar) on it:

Assembled method Namespace.SubNamespace.ClassName::MethodName

If your output has the following lines in it then you probably have a different problem to this one as it should be missing from the output when there is no Strong Name Key file:

Creating PE file   

Emitting classes:

这篇关于使用ilasm失败，但没有给出原因的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！