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

Split .NET exe file into many smaller ones

P: n/a
Hello,

We're developing application in VS2005 using vb.net.

Our application exe file is ~20mb when compiled.
Recently, we have developed auto-update feature that goes on our web-site,
authenticates through WebServices and if neccessary downloads updated
app.exe file. We had to use custom solution vs. ClickOnce for several
different reasons.

Now, problem that we have is that we would like to somehow split this exe
file into 10+ smaller dll files and update them if needed instead of
expecting users to download 20mb file when they only need update that's
100kb.

Any links, suggestions would help.
Thanks,

Vlado
Nov 28 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Hello Vlado,

I think that will involve changes at architecture level. You will have to
design the application like that, your object modal will also reflect that
design. There is no inbuilt option that you can break an EXE into multiple
DLL files by using some utility !

=============
Regards,
Jigar Mehta

VvHello,
Vv>
VvWe're developing application in VS2005 using vb.net.
Vv>
VvOur application exe file is ~20mb when compiled.
VvRecently, we have developed auto-update feature that goes on our
Vvweb-site,
Vvauthenticates through WebServices and if neccessary downloads
Vvupdated
Vvapp.exe file. We had to use custom solution vs. ClickOnce for
Vvseveral
Vvdifferent reasons.
VvNow, problem that we have is that we would like to somehow split
Vvthis exe file into 10+ smaller dll files and update them if needed
Vvinstead of expecting users to download 20mb file when they only need
Vvupdate that's 100kb.
Vv>
VvAny links, suggestions would help.
Vv>
VvThanks,
Vv>
VvVlado
Vv>
Nov 28 '06 #2

P: n/a
Hello Jigar,

I understand that this change will have to involve more than simply running
some utility but we would need some directions as to how to achieve it.

We were looking at having multiple projects within one solution but
cross-referencing would be huge burden.
Thank you for your input.
"Jigar Mehta" <ji**************@gmail.comwrote in message
news:6b*************************@msnews.microsoft. com...
Hello Vlado,

I think that will involve changes at architecture level. You will have to
design the application like that, your object modal will also reflect that
design. There is no inbuilt option that you can break an EXE into multiple
DLL files by using some utility !

=============
Regards,
Jigar Mehta

VvHello,
VvVvWe're developing application in VS2005 using vb.net.
VvVvOur application exe file is ~20mb when compiled.
VvRecently, we have developed auto-update feature that goes on our
Vvweb-site,
Vvauthenticates through WebServices and if neccessary downloads
Vvupdated
Vvapp.exe file. We had to use custom solution vs. ClickOnce for
Vvseveral
Vvdifferent reasons.
VvNow, problem that we have is that we would like to somehow split
Vvthis exe file into 10+ smaller dll files and update them if needed
Vvinstead of expecting users to download 20mb file when they only need
Vvupdate that's 100kb.
VvVvAny links, suggestions would help.
VvVvThanks,
VvVvVlado
Vv>

Nov 28 '06 #3

P: n/a
Hello Vlado,

If you are using Visual Studio 2005, having multiple projects in one solution
(even different languages!!) and referencing them is not at all a burden.
You can easily do that. Start with modularize your whole project into small
parts and utilities. If you can separate some components, move their coding
into seperate DLL file and provide wrapper if needed.

It should not be so hard.

=============
Regards,
Jigar Mehta

VvHello Jigar,
Vv>
VvI understand that this change will have to involve more than simply
Vvrunning some utility but we would need some directions as to how to
Vvachieve it.
Vv>
VvWe were looking at having multiple projects within one solution but
Vvcross-referencing would be huge burden.
Vv>
VvThank you for your input.
Vv>
Vv"Jigar Mehta" <ji**************@gmail.comwrote in message
Vvnews:6b*************************@msnews.microsof t.com...
Vv>
>Hello Vlado,

I think that will involve changes at architecture level. You will
have to design the application like that, your object modal will also
reflect that design. There is no inbuilt option that you can break an
EXE into multiple DLL files by using some utility !

=============
Regards,
Jigar Mehta
VvHello,
VvVvWe're developing application in VS2005 using vb.net.
VvVvOur application exe file is ~20mb when compiled.
VvRecently, we have developed auto-update feature that goes on our
Vvweb-site,
Vvauthenticates through WebServices and if neccessary downloads
Vvupdated
Vvapp.exe file. We had to use custom solution vs. ClickOnce for
Vvseveral
Vvdifferent reasons.
VvNow, problem that we have is that we would like to somehow split
Vvthis exe file into 10+ smaller dll files and update them if
needed
Vvinstead of expecting users to download 20mb file when they only
need
Vvupdate that's 100kb.
VvVvAny links, suggestions would help.
VvVvThanks,
VvVvVlado
Vv>

Nov 28 '06 #4

P: n/a
Wow, that's a HUGE file!

Rather than split the EXE, I would suggest you refactor your
application such that it is composed of a several projects, each of
which compiles to DLL and the main project becomes the EXE.

Is this an option available to you?

On Tue, 28 Nov 2006 09:21:54 -0600, "Vlado Jasovic"
<vladoDOTjasovicATexcelleincDOTcomwrote:
>Hello,

We're developing application in VS2005 using vb.net.

Our application exe file is ~20mb when compiled.
Recently, we have developed auto-update feature that goes on our web-site,
authenticates through WebServices and if neccessary downloads updated
app.exe file. We had to use custom solution vs. ClickOnce for several
different reasons.

Now, problem that we have is that we would like to somehow split this exe
file into 10+ smaller dll files and update them if needed instead of
expecting users to download 20mb file when they only need update that's
100kb.

Any links, suggestions would help.
Thanks,

Vlado
--

Bits.Bytes.
http://bytes.thinkersroom.com
Nov 28 '06 #5

P: n/a
Ho come it is so big?
..NET executable are typically very small unless they include resources (i.e.
any kind of file you use such as sound, picture, data model, etc...).
Perhaps you could put these resources in external assembly?
Or even plainly visible?

"Vlado Jasovic" <vladoDOTjasovicATexcelleincDOTcomwrote in message
news:14******************************@giganews.com ...
Hello,

We're developing application in VS2005 using vb.net.

Our application exe file is ~20mb when compiled.
Recently, we have developed auto-update feature that goes on our web-site,
authenticates through WebServices and if neccessary downloads updated
app.exe file. We had to use custom solution vs. ClickOnce for several
different reasons.

Now, problem that we have is that we would like to somehow split this exe
file into 10+ smaller dll files and update them if needed instead of
expecting users to download 20mb file when they only need update that's
100kb.

Any links, suggestions would help.
Thanks,

Vlado

Nov 29 '06 #6

P: n/a
UJ
We are doing pretty much exactly what you are doing except our files are
much smaller.

What I did was move a lot of the classes into DLL so they can be downloaded
separately ( although I don't because my stuff is so small - usually less
than 500 KB. )

But I have one big solution that has about 6 projects that create EXEs and 4
more that create DLLs that are used by the EXEs. One caution though - make
sure you make the EXE projects dependent on the DLLs or they won't always
get recompiled when the DLL is recompiled.

Hope this helps.

Jeff.

"Vlado Jasovic" <vladoDOTjasovicATexcelleincDOTcomwrote in message
news:14******************************@giganews.com ...
Hello,

We're developing application in VS2005 using vb.net.

Our application exe file is ~20mb when compiled.
Recently, we have developed auto-update feature that goes on our web-site,
authenticates through WebServices and if neccessary downloads updated
app.exe file. We had to use custom solution vs. ClickOnce for several
different reasons.

Now, problem that we have is that we would like to somehow split this exe
file into 10+ smaller dll files and update them if needed instead of
expecting users to download 20mb file when they only need update that's
100kb.

Any links, suggestions would help.
Thanks,

Vlado

Feb 16 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.