DLL bigger than all the other DLLs in my project combined!

[MeaningOfLights]

Hi Guys,

Love your work, its been working fantastic, my only concern is the size:

Is it possible for you guys to turn off <DebuggerSupport> and the call stack <IlcGenerateStackTraceData> and strip the symbols: <StripSymbols>?

I doubt the DebuggerSupport or StackTrace are needed because to reproduce a problem you simply need the input string & key that causes an error encrypting or decrypting. Plus you can still use WinDbg or Attach a Debugger with symbols, they're just not saved in the DLL.

[peterdettman]

AFAIK we put symbols in a companion .snupkg using the following settings when publishing:

<IncludeSymbols>true</IncludeSymbols>
<SymbolPackageFormat>snupkg</SymbolPackageFormat>
<DebugType>portable</DebugType> <!-- Implicit via default value -->

Recent releases should support trimming, which people have said helped drastically reduce the footprint within their application.

[MeaningOfLights]

I tried the trimming and no luck unfortunately. Its not a big issue but is a big question, 5MB worth of code to encrypt/decrypt, really?