Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>One thing that I've used before is implementing a <a href="http://msdn.microsoft.com/en-us/library/system.appdomainmanager.aspx" rel="nofollow noreferrer">DomainManager</a>. It's possible to customize the various <a href="http://en.wikipedia.org/wiki/Application_Domain" rel="nofollow noreferrer">application domain</a> security/binding/context's to handle complex or chicken-egg type problems with respect to pumping your data where you want ;)</p> <p>I've ususally done this from a native.exe, bootstrapping the CLR through the COM interfaces (psudo code but the order and method names are correct ;):</p> <pre><code>CorBindToRuntimeEx() SetHostControl() GetCLRControl() SetAppDomainManagerType("yourdomainmanger","info") // Domain manager set before starting runtime Start() HostControl -- GetDomainManagerForDefaultDomain() DomainManager -- Run() </code></pre> <p>Your domain manager can be any <a href="http://en.wikipedia.org/wiki/Common_Language_Runtime" rel="nofollow noreferrer">CLR</a> class library, so their's not that much more native C.</p> <p>A side note, if you were in <a href="http://en.wikipedia.org/wiki/Windows_Presentation_Foundation" rel="nofollow noreferrer">WPF</a>; I really like using the "Microsoft.DwayneNeed.Controls" method. Where you may have disperate threads with their own Dispatcher pump in the <em>same</em> UI control (not needing to resort to entirely new Window()'s).</p> <p>The unique thing about using this approach, is that even if the primary UI thread is blocked/busy (some heavy operation, scanning the filesystem, etc...), these other threads may paint/update their UIElement's without any hiccup.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload