Small exe large application

[Robert Bravery]

Hi al,,
New to VB.net. What methods should I use in ordewr to create a small exe
application that can call other libraries.
I am in the process of creating a rather large application, I don't want to
end up, when I compile and build the application to have a exe 5.6mb big
Any help pointing me in the right direction

Thanks
Robert

 

[Rick Rothstein]

Almost everybody in this newsgroup is using VB6 or lower. While you may
get a stray answer to VB.NET (including VB2003 and VB2005 which has
dropped .NET from its name) questions here, you should ask them in
newsgroups devoted exclusively to .NET programming. Look for newsgroups
with either the word "dotnet" or "vsnet" in their name.

For the microsoft news server, try these newsgroups...

microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb
microsoft.public.vsnet.general

There are some others, but these should get you started.

Rick - MVP

 

[David Fúnez]

What about DotFuscator, it comes with Visual Studio .NET.
You can find it in the Tools menu.

Have a nice day.

--
David Fúnez
Tegucigalpa, Honduras

"La Piratería Mata Las Ideas"
Desarrollador Cinco Estrellas Visual FoxPro

 

[Herfried K. Wagner [MVP]]

New to VB.net. What methods should I use in ordewr to create a small exe
application that can call other libraries.

Take a look at the class library project template. You can add class
library projects to your solution and reference these class libraries (DLLs)
from your executable project.

 

[Rick Rothstein]

Sorry... I missed the cross-post to this group (my comment was meant for
the microsoft.public.vb.general.discussion newsgroup.

Rick - MVP

 

[Randy Birch]

Wrong newsgroup - this is for VB4/5/6 (aka 'real vb', 'vb classic').

For the microsoft news server you can try one of these or some of the many
other similarly-named groups devoted exclusively to .net programming:

news://msnews.microsoft.com/microsoft.public.dotnet.general
news://msnews.microsoft.com/microsoft.public.dotnet.languages.vb
news://msnews.microsoft.com/microsoft.public.vsnet.general
news://msnews.microsoft.com/microsoft.public.vstudio.general
news://msnews.microsoft.com/microsoft.public.vstudio.setup


--


Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/


: Hi al,,
: New to VB.net. What methods should I use in ordewr to create a small exe
: application that can call other libraries.
: I am in the process of creating a rather large application, I don't want
to
: end up, when I compile and build the application to have a exe 5.6mb big
: Any help pointing me in the right direction
:
: Thanks
: Robert
:
:
:

 

[Mitchell Vincent]

Hi al,,
New to VB.net. What methods should I use in ordewr to create a small exe
application that can call other libraries.
I am in the process of creating a rather large application, I don't want to
end up, when I compile and build the application to have a exe 5.6mb big
Any help pointing me in the right direction

Thanks
Robert

Robert, if you are extremely concerned about executable size then you
really should consider using another development platform/language
(which is .NET?). If you are creating a "rather large application" then
5.6MB isn't very big at all.

I am like you in that I used to care about exe size and all that. I
don't anymore - especially since I started playing with .NET as it
produces rather large EXEs..

 

[Robert Bravery]

HI Michael,

Does'nt the exe have to load completely in memory. That to me seems to be a
complete waste, what if a user doe'nt use a particular part of the app for
some reason, but on another occasion he might use that part but not another.
The whole app sitting in memory is then completley wasted, and defies OOP
and event driven programming.

I come from a development patform, which enables one to have a very small
loader exe, all other objects remain as outside objects, and are only loaded
when called. So if I have an accounting app, the bank recon form might only
get loaded when it is needed, and all the other forms or objects that are
not needed at that time are not loaded, preserving resources.
How can I apply this principle in VB.net/C#.net.
I am not worried about large EXE per se, but more about true OOP eand event
driven programming and only loading what you want to use as apposed to
everything at once.

Thanks
Robert

 

[Josip Medved]

Does'nt the exe have to load completely in memory. That to me seems to be

a

No. Exe is mapped in VM but it isn't loaded as such. System decides
which part of it to load and which to leave on disk. BTW That is
one of reasons why you can't delete .exe while it is running...