Effect of unused methods and properties on library or executable

Question

I\'m playing around with creating a source code generator for C# (.NET). Will generating properties or methods that never get called cause my code to run slower? How about i

Answer 1

Unused methods will make the executable slightly larger. It will take a bit longer to load, and will consume more system memory.

If the application runs in a memory constrained environment you may see a slight reduction in performance.

Aside from that, you should not see a performance slowdown.

The "using" statements just allow you to write shorter versions of class names in your source code. They do not impact the file size or execution speed.

There are third party linkers that can remove unreferenced methods from a final .EXE.

Answer 2

You should consider using partial methods, especially when using code generators. A partial method, if it's not actually implemented, will be removed by the compiler.

Answer 3

The compiler is already smart enough to only list referenced assemblies in the final executable that are actually used. No need to fiddle with assembly references or using directives.

The JIT compiler will only ever generate code for methods that are actually called. So you will not have any machine code or compile time overhead due to code that is never used.

Your executable image is getting referenced through a memory-mapped file by the CLR. RAM will only be used if actual content in the DLL is used by the CLR. It depends how the IL of the methods you use is distributed through the image. There are reasonable odds that since the JIT compiler never references the IL, the image data won't be paged into RAM either. In other words, you'll lose some virtual memory space but won't consume a corresponding amount of RAM.

If your DLL is strong named and stored in a non-trusted location then the warm boot time will be slightly longer due to the larger file size.