.NET application silently fails to start when assembly missing
Posted
by chiccodoro
on Stack Overflow
See other posts from Stack Overflow
or by chiccodoro
Published on 2010-05-19T16:02:38Z
Indexed on
2010/05/19
18:40 UTC
Read the original article
Hit count: 361
I have a .NET C# winforms application which works great on my machine, but if I try to run it on another machine, it doesn't start up. No error message, no crash message, no window - nothing.
I've found that this always happens when a referenced assembly is missing. I guess this is .NET's general behavior and not specific to my app, is it?
Is there any way to configure .NET or my application such that it spits out a "referenced assembly missing" like error message in such cases?
© Stack Overflow or respective owner