By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,465 Members | 1,474 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,465 IT Pros & Developers. It's quick & easy.

Application started from second application domain works much slower.

P: n/a
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
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.