Clever Geek Handbook

Resource size nesting

I have an application developed in C # that does some things. I decided to include .msi

which I want to call during the process. The size executable

is about 5MB and the size .msi

is about 150MB. But when a new executable with embedded .msi is compiled, now 400MB !!

Why is this? Does the resource attachment increase the final size .exe

?

+3


source to share


1 answer


I ended up outputting because of what the user posted here .

When I add .msi

mine as a resource, I have two copies of the same file at the end. This is why I am doubling the size of my final executable.

  • One instance of mine .msi

    because it is linked as a resource in my project
  • Another copy is that compiling the project links another copy of that file


So, I did the following:

  • Remove .msi

    fromResources

  • In the folder I wanted, I added it by simply typing Add->Existing Item

  • Then I changed Build action

    to .msi

    to Embedded Resource

    and was built into my application, but it doesn't get called twice as it doesn't countResource

More or less this is the answer.

0


source






More articles:


All Articles