By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,642 Members | 1,474 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,642 IT Pros & Developers. It's quick & easy.

Manifest Resource increase in size with Localizable set to True.

P: n/a
I did a little experiment during localization of my software (or at least
preparations for localization) - without adding any language resources, I
just went through changing the Localizable property of each form from False
to True. I noticed that the resulting Executable instead of being 4mb was
closer to 8mb. This suprised me. So I did a little experiment. I set the
localizable flag to false on one noddy form and then checked the indices
into the manifest resources. It turns out that this one form with
Localizable switched off uses ~ 16890 bytes, but with Localizable switched
on it uses ~ 77956 bytes. This is true for much of the application. Can
anyone account for this inflation?

Thanks.
Nov 21 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
what are the differences in sized when compiled in "release" rather than
"debug"?
"Robin Tucker" <un********@duetospam.com> wrote in message
news:dg*******************@news.demon.co.uk...
|I did a little experiment during localization of my software (or at least
| preparations for localization) - without adding any language resources, I
| just went through changing the Localizable property of each form from
False
| to True. I noticed that the resulting Executable instead of being 4mb was
| closer to 8mb. This suprised me. So I did a little experiment. I set
the
| localizable flag to false on one noddy form and then checked the indices
| into the manifest resources. It turns out that this one form with
| Localizable switched off uses ~ 16890 bytes, but with Localizable switched
| on it uses ~ 77956 bytes. This is true for much of the application. Can
| anyone account for this inflation?
|
| Thanks.
|
|
Nov 21 '05 #2

P: n/a
I don't think .NET is like Ye Olde .CPP executables in that it tends to
carry around a lot of meta-information regardless of debug or release
versions. FYI, it's about 100k different. Which is tiny compared to the
4mb difference I'm thinking about.
"steve" <a@bc.com> wrote in message news:OW*******************@fe05.lga...
what are the differences in sized when compiled in "release" rather than
"debug"?
"Robin Tucker" <un********@duetospam.com> wrote in message
news:dg*******************@news.demon.co.uk...
|I did a little experiment during localization of my software (or at least
| preparations for localization) - without adding any language resources,
I
| just went through changing the Localizable property of each form from
False
| to True. I noticed that the resulting Executable instead of being 4mb
was
| closer to 8mb. This suprised me. So I did a little experiment. I set
the
| localizable flag to false on one noddy form and then checked the indices
| into the manifest resources. It turns out that this one form with
| Localizable switched off uses ~ 16890 bytes, but with Localizable
switched
| on it uses ~ 77956 bytes. This is true for much of the application.
Can
| anyone account for this inflation?
|
| Thanks.
|
|

Nov 21 '05 #3

P: n/a

"Robin Tucker" <un********@duetospam.com> wrote in message
news:dg******************@news.demon.co.uk...
|I don't think .NET is like Ye Olde .CPP executables in that it tends to
| carry around a lot of meta-information regardless of debug or release
| versions. FYI, it's about 100k different. Which is tiny compared to the
| 4mb difference I'm thinking about.

yes and no...tending to be more on the yes-side. how much meta-data remains
really depends though, and typically most of the meta revolves around your
own code much of the time. i would have expected the difference to be much
more than 100k. i really can't account for the localization bloat. have you
tried importing the namespace(s) you need and massaging your forms at
run-time? what functionality do you need?
Nov 21 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.