nugetfuzz: stage the forward targets of facade assemblies
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
从 TestTools/nugetfuzz.cs 开始,追踪完整 nuget.org catalog 扫描期间使用的 assembly closure staging。重现 storyteller 5.4.0 的警告,然后验证 facade ExportedType 的转发目标会以传递方式进行 staging,并且受影响的完全解析 package 不再发出这些警告。
由索引模型根据 Issue 内容生成。
描述
During a full nuget.org catalog sweep with TestTools/nugetfuzz.cs, the largest group of decompiler warnings in packages whose references all resolved turned out to be a staging gap in the tool itself, not a decompiler problem.
Symptom. netstandard2.0 / netcoreapp packages (storyteller, nancy, csla-core, fluentnhibernate, nhibernate, specflow, neo4jclient, ...) produce Unknown result type / Expected O, but got Unknown warnings even though the run reports every reference resolved.
Witness. storyteller 5.4.0, StoryTeller.Util.XmlExtensions:
IL_0001: call bool [netstandard]System.IO.File::Exists(string) // resolves fine
IL_0008: newobj instance void [netstandard]System.Xml.XmlDocument::.ctor() // goes Unknown
Root cause. TypeRefs in netstandard-targeted assemblies are scoped to the netstandard facade, which only contains ExportedType forwards. Forwards whose target assembly happens to be in the staged closure resolve; forwards to assemblies outside it (System.Xml.* -> System.Xml.ReaderWriter, System.Dynamic.* -> System.Linq.Expressions) dead-end, the type becomes UnknownType, and ILReader warns at every use. The per-assembly "refs resolved" counter stays green because the facade itself resolved.
Proof it is not the decompiler. Standalone ilspycmd (which probes the installed runtime, where the forward targets exist) decompiles the same types from the same DLLs with zero warnings, so the forwarder-following logic is fine.
Suggestion. When staging an assembly closure, additionally stage the assemblies referenced by the ExportedType table of any facade included in the closure (transitively). This removes the largest warning group from sweep results and makes the WARNING channel meaningful for fully-resolved packages.
Filed by an AI agent (Claude, claude-fable-5, Claude Code) on behalf of @siegfriedpammer; findings verified against ILSpy master on 2026-08-31.
- 主要语言
- C#
- 星标
- 27.1k
- 派生
- 3.8k
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 44
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
icsharpcode/ILSpy 的其他 Issue
-
External UI
难度 1/5 1-3 小时 新手友好度 75/100
icsharpcode/ILSpy#4284 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 55/100
icsharpcode/ILSpy#4357 ·
维护者通常 1 天内回复
-
Misdecompilation of a lazy initialization pattern可能已有人在做 @siegfriedpammer 于 5 天前认领。 未关闭Bug Decompiler
难度 4/5 3-5 天 新手友好度 20/100
icsharpcode/ILSpy#4349 ·
维护者通常 1 天内回复
-
Bug
难度 4/5 3-5 天 新手友好度 45/100
icsharpcode/ILSpy#4343 ·
维护者通常 1 天内回复
-
AI
难度 4/5 1-2 天 新手友好度 55/100
icsharpcode/ILSpy#4300 ·
维护者通常 1 天内回复
查看 icsharpcode/ILSpy 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
umbraco/Umbraco.Automate#612 ·
维护者通常 1 天内回复
-
崩溃日志只按 CRLF 分行未关闭
难度 2/5 1-3 小时 新手友好度 72/100
PCL-Community/PCL-CE#3872 ·
维护者通常 1 天内回复
-
type:task ux
难度 2/5 1-3 小时 新手友好度 72/100
elsa-workflows/elsa-foundation#5253 ·
维护者通常 1 天内回复