>
>The events are the thing I am not clear on. Since I am connecting to an external device via its own Dot NET API I am subscribing to events in this class and handleing them here only. Also since it is a wrapper class I have defined my own events inside this class and am raising them as needed and subscribing to them in my application classes. Will this be an issue for me this way?

I'm not sure if it will be an issue for you or not. When your event fires it will be firing on the other (new) thread that was created for the separate assembly. For UI, yes, you always have to marshal back to the UI thread. For other threads, I don't know if there is quite as easy of a way to marshal across threads. I'd guess probably not since I'd think you'd probably need some sort of event loop, so hopefully that isn't something you need to do ;-)

>Thanks for the help, I very much appreciate it. Somehow I always dumbly thought a seperate assembly would just always run in its own thread. Apparently not thought out, but glad I am getting this sorted out now.

It's not always really clear what's going on behind the scenes.