CSharp/C#, How to start a thread in a new AppDomain ?

microsoft.public.dotnet.languages.csharp - General discussion regarding the C# .NET programming language. including best practices on developing with C# in VS, documentation, setup, and samples.


CSharp/C# >> How to start a thread in a new AppDomain ?

by Polaris » Sat, 06 Sep 2008 21:26:50 GMT

Hi C# Experts:

I have 2 threads and I like to run them in seperate AppDomains.

In other words, I want to start 2 new AppDomains and then run a thread
within each of the AppDomains. How to do it?

Thanks
Polaris

Top

CSharp/C# >> How to start a thread in a new AppDomain ?

by Dave » Sat, 06 Sep 2008 23:21:05 GMT


This bit of code should point you in the right direction.

public class Program
{
static void Main(string[] args)
{
AppDomain domain = AppDomain.CreateDomain("SecondDomain");
System.Threading.Thread.CurrentThread.Name = "Thread 2";

// Thread.Start in first domain
System.Threading.Thread thread = new
System.Threading.Thread(SomeMethod);
thread.Name = "Thread 1";
thread.Start();

// Current thread, for simpliicty, second domain
domain.DoCallBack(new CrossAppDomainDelegate(SomeMethod));

Console.ReadLine();
}

static void SomeMethod()
{
Console.WriteLine("Domain: " +
AppDomain.CurrentDomain.FriendlyName);
Console.WriteLine("Thread: " +
System.Threading.Thread.CurrentThread.Name );

}
}

The CrossAppDomainDelegate is a good tool for threading across appdomain
boundaries.

HTH,
D. Swicegood
Top
Similar Threads

1. Start a new thread from an existing thread, which was started from a timer

2. Start a new thread from an existing thread, which was started from a timer - Microsoft .NET Framework

3. i want to create new thread for new appDomain 

can i do it this way :

from the defualt AppDomain :
create thread.
from the  start function of the new thread , create new AppDomain,and then
create my class through the AppDomain .

this way is ok ?

or there is other way to do that ?

4. Start a new thread and capture the event happening in the thread Compact Framework - CSharp/C#

5. AppDomain problem : Creating Controls in a separate AppDomain to display in Main AppDomain 

Visual Studio 2005, .NET FrameWork 2.0, C#, WinForms Application

Hi,

I've read the recent posts by and to 'Thunderbird' (and learned a lot, 
thanks, from the usual masters Skeet and Paladino, and others) which involve 
AppDomains in a remoting scenario, but I think the issue I am working with 
... while related ... is sufficiently different to warrant a new thread.

I'm also working on a plug-in architecture it's for a WinForms based 
project.

At run-time I "discover" and load all the Plug-Ins that match a MainApp 
Interface with no problem.

I find I can pass complex objects (like the TreeNode of a TreeView) to the 
plug-ins' AppDomain, and modify certain properties and have the result show 
up in the Main App's UI, no problem.

What I find I can't do ... I assume because WinForm objects like a TreeView 
and the Nodes collection object of a TreeView are passed as proxies ... is 
create new Nodes in the plug-in app domain and then pass them back to the 
Main app and put them in the TreeView in the UI there.

Error trying to create a new TreeView Node in the Plug-In appDomain (yes, 
Plug-Ins do contain references for WinForms) :

"SerializationException Crossed an AppDomain Boundary"

Type 'System.Windows.Forms.Control+ControlCollection' in assembly
'System.Windows.Forms, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' is not marked as serializable.

"Ideally" I'd like to pass the Plug-In a bounding rectangle definition, have 
it create a collection of controls, and get those controls back to the Main 
AppDomain and plug them into a Panel and then have the Plug-In, based on the 
state of its controls, do the "right thing" to conjure up whatever objects 
it wants to create and get those objects back to the Main App for 
display/use in the main UI.

At this point I believe that is simply not possible ... although Jon Skeet's 
comments in his reply to Thunderbird are still inviting me to reconsider and 
re-think.

What I do believe is most probable is that there is an optimum architecture 
for a situation where :

1. you want to load plug-ins in a separate appDomain (in T'Bird's case one 
appDomain per plug-in). so you can unload at will.

2. you want the plug-in to specify its run-time user interface to the Main 
appDomain in some terse, easily parsable form.

3. you want the Main appDomain to present the Plug-In's controls/widgets in 
the main UI, let the user alter their state at run-time.

4. you want the Plug-In (through direct action at run-time) to trigger some 
process that results in modification of complex objects, or creation of new 
ones in the Main appDomain.

Appreciate any feedback. I have examined the various add-in/plug-in projects 
of CodeProject, the usual books (Petzold, Sells, Liberty, Gunnerson).

It would help me greatly if I had a better sense of exactly what a "proxy" 
is, and I appreciate any referrals to learning materials in that area.

thanks !

Bill Woodruff
dotScience
Chiang Mai, Thailand

6. appdomain unload ->System.Threading.ThreadAbortException: Thread was being aborted - CSharp/C#

7. does ShowDialog start new thread ? 

Hi,

Does Form.ShowDialog() start new thread ?
If yes how is solved cross-thread operations?

Thx

8. Starting a new Thread vs. ThreadPool - CSharp/C#