G
Gregg Walker
Hi all,
Does anyone know howto receive a notification (event) when the assembly loaded by AppDomain.ExecuteAssembly loads the startup method
and begins executing it?
I want to give the user a visual (hour glass, etc.) that an application is being loaded while AppDomain.ExecuteAssembly is loading
assemblies. Once it begins executing the loaded assembly I want to make the visual go away. I'm using no touch deployment of
windows forms apps that are hosted on a Win2003 Server. I have a shell launcher app that calls ExecuteAssembly on the exe assembly
at the specified URL.
I tried using AppDomain.AssemblyLoad event but it fires every time each referenced assembly in the exe is loaded and I have no way
of knowing when the assembly actually begins executing.
As it stands now every time the launcher shell is started I get an AppStarting cursor until it is running (usually only takes a
second or less) but the cursor disappears from there on until the windows form app is actually up and running. This may take much
longer than a second or two because of network delays and assembly sizes. End result is the user thinks that nothing is happening
and tries to start the launcher shell again.
Thanks for any help.
Sincerely,
Gregg Walker
Does anyone know howto receive a notification (event) when the assembly loaded by AppDomain.ExecuteAssembly loads the startup method
and begins executing it?
I want to give the user a visual (hour glass, etc.) that an application is being loaded while AppDomain.ExecuteAssembly is loading
assemblies. Once it begins executing the loaded assembly I want to make the visual go away. I'm using no touch deployment of
windows forms apps that are hosted on a Win2003 Server. I have a shell launcher app that calls ExecuteAssembly on the exe assembly
at the specified URL.
I tried using AppDomain.AssemblyLoad event but it fires every time each referenced assembly in the exe is loaded and I have no way
of knowing when the assembly actually begins executing.
As it stands now every time the launcher shell is started I get an AppStarting cursor until it is running (usually only takes a
second or less) but the cursor disappears from there on until the windows form app is actually up and running. This may take much
longer than a second or two because of network delays and assembly sizes. End result is the user thinks that nothing is happening
and tries to start the launcher shell again.
Thanks for any help.
Sincerely,
Gregg Walker