[RESOLVED ..for the time being :D]Is .NET inherently flawed with RaiseEvents

[MalcolmCarmen]

I've made at least two fairly large apps, both of which have utterly failed. Why? They are both server applications, so it opens a new Socket thread, and some classe(s) for each session. So let's say that an event gets called - even an async event:

1. RaiseEvent MyEvent()
2. MyEvent() is raised on the host object...
3. AnotherSub() is called
4. AnotherSub() sets the object that just called the event to nothing
5. Normally, the "chain of events" ends here, but the object that called it was just terminated on step #4! The result...

"Thread (gibberish here) has exited with code 0" in debug window - a nice silent error that indicates something went horribly wrong, leaving me to guess at what.

So here's my question: Am I doing something other new people are doing (VB6 was always fine with this kind of stuff) wrong, or are my apps in need of serious overhall to avoid these "silent death" errors. It is endlessly annoying, and has killed all my large projects thus far!

edit: Oh yes, not only does the thread exit, but things "stop working" ... after the thread has died, it generally results in a lifeless program that no longer works until you restart it!