I have no idea what FoxPro was doing... probably storing the forms in a data
file and "building" them on the fly. This sounds pretty slow to me.
I'm happier with anything that speeds up the process of loading each form.
Dot net is no speed demon during load-up, no argument there, but I'm not
that interested slowing it down any further.
Compiled code is fast code.
The size of the EXE matters once, during install, and then only in terms of
the number of seconds difference it takes to download a 100K EXE over an
120K EXE. That's not a lot of difference. Loading a form happens all the
time.
My $0.02
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Sezai Altınok" <se**********@hotmail.com> wrote in message
news:ux**************@TK2MSFTNGP12.phx.gbl...
i think i couldn't make myself clear. i'm not talking about making a change
in the code behind that will effect the design. for example, in asp.net if
you make a change only in the designer not in the code behind, you simply
run the page from the browser to see the change (you do not rebuild the
project). as in this example, but this time i'm making a change in the
code
behind. for instance, changing a button click event to do a different job.
do i HAVE TO rebuild the project. also, if you are making a big project,
everytime you add a new form into it the exe file will become larger and
larger. i don't want this. i want my exe file is as small as possible and
use the forms as resource files.
thanks for your replies...
"Sezai Altınok" <se**********@hotmail.com> wrote in message
news:#f**************@TK2MSFTNGP12.phx.gbl... is it possible to build a project without recompiling the forms like in
FoxPro?
i mean in foxpro when you make some changes even in the code part of a
form you can see the effect without a recompile.