VB.net simple threaded GUI based program. Where to put the thread?

When you inherit from a class, you are implying an IS A relationship. EDComms is not a thread. Having it manage the thread is one approach, or you might have a background worker external to the class all together.

But I would say the only option that shouldn't be an option, is the inheritence option.

Really, either is OK. It's more a matter of what you want the thread to mean from a design standpoint. Is the EDComms object going to be doing the work itself or would you rather have the EDComms object simply wrap the worker and provide an interface to communicate with it.

Personally, I like your choice better, I think it makes logical sense, but that's just my opinion.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.