Huge EXE file size

[anandsoni]

Guys, I have an application that has so many components/modules
embeded into it and the file when built has the size of around 100MB.

The application runs little slow but I cannot think of other potential
problems that I can have with the application size? Can you guys shed
some disadvantages with it please?

[Rad [Visual C# MVP]]

On Sun, 19 Aug 2007 22:51:12 -0700, an*******@gmail.com wrote:

>Guys, I have an application that has so many components/modules
embeded into it and the file when built has the size of around 100MB.

The application runs little slow but I cannot think of other potential
problems that I can have with the application size? Can you guys shed
some disadvantages with it please?

100 MB? Something is *very* wrong! DO you have embedded resources like
movies, images, etc? Also, you might want to split the application
into several class libraries

--
http://bytes.thinkersroom.com

[ThunderMusic]

Hi,
One BIG disadvantage is if you want to make an update for one of these
component or event your app itself that should be a smaller exe, you have to
update the whole 100MB... It can be very painful for your internet users to
download it and it could also empty your bank account to pay the bandwidth
you'll use for those updates... ;)

I say, keep it as small as possible don't embed your libraries, medias, et
al. in your exe, keep each file simple. By modules, are you saying like
plug-in modules or libraries? or VB-Like modules? Can they be "modularized"
into many smaller libraries?

I hope it helps

ThunderMusic
<an*******@gmail.comwrote in message
news:11**********************@q3g2000prf.googlegro ups.com...

Guys, I have an application that has so many components/modules
embeded into it and the file when built has the size of around 100MB.

The application runs little slow but I cannot think of other potential
problems that I can have with the application size? Can you guys shed
some disadvantages with it please?