Geek Answers Handbook

.NET ILMerged assemblysies performance

I have two .NET libraries: "Foo.Bar" and "Foo.Baz".
"Foo.Bar" is standalone, and "Foo.Baz" refers to "Foo.Bar".

Assuming I do the following:

  • Use ILMerge to combine "Foo.Bar.dll" with "Foo.Baz.dll" into "Foo1.dll".
  • Create a new solution containing the enthusiasm of both “Foo.Bar” and “Foo.Baz” (since I have access to their source code) and compile it into “Foo2.dll”.

Will there be any performance differences between Foo1.dll and Foo2.dll when using their functions from an external project? If so, how significant is this performance difference, and is it a one-time (at boot time) or current difference? Are there any other advantages or disadvantages to any approach?

+7
performance assemblies ilmerge
source share
1 answer

I am sure that this would not produce exactly the same IL, but it would be very close, and I can not imagine any noticeable difference between the two methods. Besides the fact that the ILMerge method is probably more convenient and easy to maintain, I think that both solutions will have the same result.

+3
source share

More articles:


All Articles