Hi Boris,
> I notice the following strange behavior of the applications running under
> .NET Framework.
[quoted text clipped - 16 lines]
> MyApp.exe is allowed to start in order to crash right after attemp to use any
> functionality from missing dependent assembly?
Nope; it's working just as expected. The runtime will only load an assembly
when it needs to. This, btw, helps insure you don't load things you're not
gonna use, and, it enables some interesting scenarios with web-distributed
rich client applications (since you only have to download when you use it;
what you don't use doesn't need to be transferred at all!)

Signature
Tomas Restrepo
tomasr@mvps.org
Boris - 30 Nov 2004 02:55 GMT
OK, this is not , this is "feature".
But how can I prevent the ugly crashes in described above situation and exit
gracefully?
Thanks
Boris
"Tomas Restrepo (MVP)" wrote:
> Hi Boris,
>
[quoted text clipped - 29 lines]
> rich client applications (since you only have to download when you use it;
> what you don't use doesn't need to be transferred at all!)
Nishant S - 30 Nov 2004 05:06 GMT
Exception Handling :-)

Signature
Regards,
Nish [VC++ MVP]
http://www.voidnish.com /* MVP tips tricks and essays web site */
http://blog.voidnish.com /* My blog on C++/CLI, MFC, Whidbey, CLR... */
> OK, this is not , this is "feature".
> But how can I prevent the ugly crashes in described above situation and exit
[quoted text clipped - 38 lines]
> > rich client applications (since you only have to download when you use it;
> > what you don't use doesn't need to be transferred at all!)