.NET ILMerged 程序集的性能
我有两个 .NET 库：“Foo.Bar”和“Foo.Baz”。
“Foo.Bar”是独立的，而“Foo.Baz”引用“Foo.Bar”。
假设我执行以下操作：
- 使用 ILMerge 将“Foo.Bar.dll”与“Foo.Baz.dll”合并到“Foo1.dll”中。
- 创建一个包含“Foo.Bar”和“Foo.Baz”整体的新解决方案（因为我可以访问它们的源代码），并将其编译为“Foo2.dll”。
当从外部项目使用 Foo1.dll 和 Foo2.dll 的功能时，它们的性能会有什么差异吗？如果是这样，这种性能差异有多大，是一次性的（负载时？）还是持续的差异？这两种方法还有其他优点或缺点吗？
I have two .NET libraries: "Foo.Bar" and "Foo.Baz".
"Foo.Bar" is self-contained, while "Foo.Baz" references "Foo.Bar".
Assuming I do the following:
- Use ILMerge to merge "Foo.Bar.dll" with "Foo.Baz.dll" into "Foo1.dll".
- Create a new solution containing the entirity of both "Foo.Bar" and "Foo.Baz" (since I have access to their source code), and compile this into "Foo2.dll".
Will there be any differences in the performance of Foo1.dll and Foo2.dll when using their functionality from an external project? If so, how significant is this performance difference, and is it a once-off (on load?) or ongoing difference? Are there any other advantages or disadvantages with either approach?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我确信它不会产生完全相同的 IL，但它会非常接近，我无法想象这两种方法之间有任何明显的差异。除了 ILMerge 方法可能更方便且可维护这一事实之外，我认为这两种解决方案都会有相同的结果。
I'm sure it wouldn't produce exactly the same IL, but it would be extremely close and I can't imagine any appreciable difference between the two methods. Other than the fact that the ILMerge method is probably more convenient and maintainable, I think both solutions would have the same outcome.