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
"Mitchell Vincent" <mi**************@gmail.com> wrote in message
news:O1**************@TK2MSFTNGP14.phx.gbl...
Robert Bravery wrote: 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..
--
- Mitchell Vincent
- kBilling - An easy and affordable billing solution
- http://www.k-billing.com