Apps slow to launch from Network Location

[madangelo]

Applications developed using Framework 2.0 and installed on a network
location take a considerable amount of time to launch. This was never the
case with prior Framework versions.

For example, an application can take almost a minute just to display the
Splash screen. Not an issue when executable is stored on the local machine,
but due to the number of users we like to install all of our applications on
the network.

Any ideas or suggestions?

Thanks.

[Jim Wooley]

Applications developed using Framework 2.0 and installed on a network

location take a considerable amount of time to launch. This was never
the case with prior Framework versions.

For example, an application can take almost a minute just to display
the Splash screen. Not an issue when executable is stored on the
local machine, but due to the number of users we like to install all
of our applications on the network.

Read up on Click Once deployment. You deploy to the server. The user dynamically
pulls down updates from the server and executes them from their local computer.
There may be an initial delay, but the remainder should be fully compiled.
Jim Wooley
http://devauthority.com/blogs/jwooley/default.aspx

[madangelo]

I'll look into the ClickOnce, but why is this an issue with Framework 2 and
not with prior versions?

Thanks

"Jim Wooley" wrote:

Applications developed using Framework 2.0 and installed on a network
location take a considerable amount of time to launch. This was never
the case with prior Framework versions.

For example, an application can take almost a minute just to display
the Splash screen. Not an issue when executable is stored on the
local machine, but due to the number of users we like to install all
of our applications on the network.

Read up on Click Once deployment. You deploy to the server. The user dynamically
pulls down updates from the server and executes them from their local computer.
There may be an initial delay, but the remainder should be fully compiled.
Jim Wooley
http://devauthority.com/blogs/jwooley/default.aspx