Keeping LinqPad "alive" to test events

SteffenDyhrNielsen

Hi...

Is there a common best practice pattern for this, before I start a walkabout in the wilderness?

I´d like to use linqpad to test events fired from a COM interface.

Thx....

( ATM I´m popping up a MessageBox to keep linqpad running, but it seems a bit hmmmm )

Tormod

The appdomain isn't killed just because the code is done. Check this out : http://share.linqpad.net/kgokl8.linq

SteffenDyhrNielsen

Thanks Tormod. Why do you specify the thread? Seems my question is a matter of preference, so on a pure academic level: Wonder what solution is the most efficient to keep a thread alive....

Tormod

By creating it and not killing it....?
Do I misunderstand your question? If you are subscribed to events and they fire, the continuation will also execute. BTW, have you checked out the RX model?

SteffenDyhrNielsen

Hey Tormod.. The reason I was wondering about the extra thread initiation is that a sole while(true){...} does the job just as well.. I´ll check out the RX thing.. Thanks again.