Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7505139
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 29, 20262026-05-29T21:48:29+00:00 2026-05-29T21:48:29+00:00

Is there a tool that can explain the size of a .NET assembly (executable

  • 0

Is there a tool that can explain the size of a .NET assembly (executable or DLL file)?

In the olden days, there was an IDE extension that would detail the space used by a project.

It should show the large code files:

Enter image description here

And data resources:

Enter image description here

Is there such a thing for the .NET world?

I really thought that moving to .NET, and no longer having to build the entire VCL into the executable, that executable sizes would shrink.

Bonus Reading

  • Analyze space used by .NET assembly
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-29T21:48:30+00:00Added an answer on May 29, 2026 at 9:48 pm

    The standard SDK took ILDASM (IL Disassembler), had the “Statistics” option in the View menu, which broke it down like this:

     File size            : 3072
     PE header size       : 512 (456 used)    (16.67%)
     PE additional info   : 167               ( 5.44%)
     Num.of PE sections   : 2
     CLR header size     : 72                 ( 2.34%)
     CLR meta-data size  : 1572               (51.17%)
     CLR additional info : 0                  ( 0.00%)
     CLR method headers  : 15                 ( 0.49%)
     Managed code         : 77                ( 2.51%)
     Data                 : 512               (16.67%)
     Unaccounted          : 145               ( 4.72%)
    
     Num.of PE sections   : 2
       .text    - 2048
       .reloc   - 512
    
     CLR meta-data size  : 1572
       Module        -    1 (10 bytes)
       TypeDef       -    4 (56 bytes)      0 interfaces, 0 explicit layout
       TypeRef       -   15 (90 bytes)
       MethodDef     -    4 (56 bytes)      0 abstract, 0 native, 4 bodies
       FieldDef      -    2 (12 bytes)      0 constant
       MemberRef     -   15 (90 bytes)
       ParamDef      -    4 (24 bytes)
       CustomAttribute-   13 (78 bytes)
       StandAloneSig -    1 (2 bytes)
       Assembly      -    1 (22 bytes)
       AssemblyRef   -    1 (20 bytes)
       Strings       -   571 bytes
       Blobs         -   336 bytes
       UserStrings   -     8 bytes
       Guids         -    16 bytes
       Uncategorized -   181 bytes
    
     CLR method headers : 15
       Num.of method bodies  - 4
       Num.of fat headers    - 1
       Num.of tiny headers   - 3
    
     Managed code : 77
       Ave method size - 19
    

    This should provide a good starting point.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Is there a tool that can reflect a .Net Assembly and gets its metadata,
Is there a tool that can generate sequence diagrams from running .NET code?
Is there a tool that can analyse my .NET code (C# and VB.NET )
Is there any tool that can read a WSDL file and based on the
Visual Studio 2010 .NET 3.5 Is there any tool that can trace the http
Is there any tool that can parse a valid C program and generate a
Is there a tool that can parse C++ files within a project and generate
Is there a tool that can list the exact versions and public keys of
Is there some tool that can automatically convert the following c style code A
Possible Duplicate: Is there a tool that can display a SVN repository visually (

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.