469,322 Members | 1,579 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,322 developers. It's quick & easy.

Application started from second application domain works much slower.

Hello, All.

This is a .Net question, not precisely C#.

I have a quite heavy Windows Forms application. I'm using third party custom controls
(i.e. most of controls on the forms use custom painting using .Net + GDI+). I have compared the
performance of application when it was started standalone (from the shell) and from other .Net application
using new application domain and AppDomain.ExecuteAssembly(); the application in second AppDomain showed
very poor performance. What is the reason for such poor operation?

Here comes the code for launcher:
using System;

namespace DomainLoader
{
class App
{
static void Main(string[] args)
{
AppDomainSetup setup = new AppDomainSetup();
setup.ApplicationBase = AppDomain.CurrentDomain.BaseDirectory;
setup.LoaderOptimization = LoaderOptimization.SingleDomain;
AppDomain domain = AppDomain.CreateDomain("dummy", null,
setup);
domain.ExecuteAssembly(args[0]);
}
}
}

Shared assemblies can not be a penalty, because SingleDomain optimization is used.

What can be the reason of such a poor performance?

---
Dmitry Kostenko
Stip underscores from email to reply directly.

Nov 15 '05 #1
0 965

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Keith Jakobs, MCP | last post: by
11 posts views Thread by Jason | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by suresh191 | last post: by
reply views Thread by mdpf | last post: by
reply views Thread by harlem98 | last post: by
reply views Thread by listenups61195 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.