Anyway to speed up form loading?

[m1k3l]

Does anyone know of anyway that it would be possible to speed up the process of loading forms.

With VB6, forms (simple ones) was extremely fast but with VB.net, the initial loading of a form (even the simplest one) takes very long. Although it gets better once it's loaded once and the reloaded the next time (almost instanttaneous), but the first time loading gives a bad impression to any user that .net is actually much slower.

Is there anyway at all to speed things up?

[Pirate]

format C:
.
.
.
.
.
.
.
kiddig I'm really suffering from that as well.

[wyrd]

I don't think there is. As I understand it, when you first load up the form the JIT compiler has to actually compile it, which is why they don't pop up right away the first time you run them. Java also has this problem (although in a different way as Java is interpreted where .NET is compiled).

To be honest I wish Micrsosoft would give us a choice to actually straight up just compile programs to native code for a targetted OS using the JIT or to compile with with MSIL so it can be platform independant. It should be our choice, not MSIL by default.

[Pirate]

but I guess MS invented this tricky way to secure the code as much as possible.

[m1k3l]

the ngen.exe utility in the framework's bin directory is suppose to compile a native image (for running in windows) and store it in the gac to speed things up so that it won't have to recompile every time.

I've tried it but it doesn't seem to help much.

Anyone had better luck with the ngen utility?

[mohdali]

Hi guys, I am using Vb.Net 2008 and I am having the exact same issue as forms first load is very slow and it gets better in subsequent loads of the same form. Anyone had an idea of using Ngen with VS? Please help..

[techgnome]

To be honest I wish Micrsosoft would give us a choice to actually straight up just compile programs to native code for a targetted OS using the JIT or to compile with with MSIL so it can be platform independant. It should be our choice, not MSIL by default." .... this statement intrigues me... as it's contradictive... you're asking for the option to use JIT OR MSIL.... as if they can be used independently...

When you compile an app.... it gets compiled to MSIL ... when you then run the app, the JIT takes over, "finishes" the compiling and runs the app... So the choices should be MSIL/JIT OR full-compile to native code.

However... there's an issue with that. What to do about the framework? If you did a full native code compile, how do you deal with the FW linked assemblies?

-tg

[techgnome]

GAH! DANG IT! .... Dang blast it... I didn't notice the age on this thread.... grrrr!