.NET Load time after OS reboot?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have created a distributed app, with a Windows Forms Client and a Business
Web Service.

The Smart Client is partly a href/exe (The exe is loaded as a href/exe, the
exe contains a Smart Assembly block that loads the rest of the app).

If I place a MessageBox as the first thing in my exe, it takes up to a
minute to get to that point (first thing in my .NET code). If the computer
has just booted. Does the .NET framework need to load the first time the OS
uses a .NET application? If so - is there anyway to force a preload at
bootup????


The OS is Windows 2000, im trying to get the customer to test my app on a XP
client.
 
If I place a MessageBox as the first thing in my exe, it takes up to a
minute to get to that point (first thing in my .NET code). If the computer
has just booted. Does the .NET framework need to load the first time the OS
uses a .NET application? If so - is there anyway to force a preload at
bootup????
Click to expand...
A minute is somehow long, but as far as I know the .NET is not preloaded
when the OS starts.
It loads the very first time a .NET program is executed.

One probal solution I can think of is to load a small .NET program in the
startup folder that loads the .NET framework.
 
Thanks for Olaf's quick response!

Hi,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that when you place a MessageBox as the
first thing in your exe, the app starts up very slowly. If there is any
misunderstanding, please feel free to let me know.

I think what you suppose is correct that .NET assembly loads the first time
a .NET program is executed. Do you mean that if you don't put the
MessageBox at startup, everything works fine? If so, could you post some of
your startup code here, and explain how the app starts more detail?

I suppose that you app is hosted in IE and starts up when a link is clicked
from a web page. If so, this might be true, because the .NET CLR requires
to check smart client for security issues. It might takes a lot of time.

HTH.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Back
Top