Re: Loading assemblies from another AppDomain
- From: "Vagif Abilov" <vagif@xxxxxxxxx>
- Date: Sat, 21 May 2005 19:04:55 +0200
Unfortunately this won't help. Private bin path can't lie outside the
application base, i.e. it's just a hint to searh in other sub-directories.
It can't be set to any other directory on the machine.
Vagif
"Gunter Prossliner" <gpointprossliner@xxxxxxxxxxxx> wrote in message
news:A161CD49-3BA7-4452-8EDB-0F9782535B63@xxxxxxxxxxxxxxxx
> Hi Vagif!
>
>> My application creates an AppDomain and sets is base directory outside
>> the
>> directory of the creator. Then it needs to load in a newly created domain
>> an
>> assembly that is installed in the original (creator) domain. And fails,
>> of
>> coures, because new domain does not have this directory in it's probing
>> path.
>
> Have you checked the PrivateBinPath / PrivateBinPathProbe Properties from
> the AppDomainSetup class?
>
> // Set up the AppDomainSetup
> AppDomainSetup setup = new AppDomainSetup();
> setup.ApplicationBase = "(some directory)";
> setup.PrivateBinPathProbe = "(probe directory)";
>
> // Set up the Evidence
> Evidence baseEvidence = AppDomain.CurrentDomain.Evidence;
> Evidence evidence = new Evidence(baseEvidence);
> evidence.AddAssembly("(some assembly)");
> evidence.AddHost("(some host)");
>
> // Create the AppDomain
> AppDomain newDomain = AppDomain.CreateDomain("newDomain", evidence,
> setup);
>
>
> OK?
> br, GP
.
- References:
- Loading assemblies from another AppDomain
- From: Vagif Abilov
- RE: Loading assemblies from another AppDomain
- From: Günter Prossliner
- Loading assemblies from another AppDomain
- Prev by Date: Re: how to modify a existing resource file
- Next by Date: Re: Default assemblies and CorBindToRuntimeEx
- Previous by thread: RE: Loading assemblies from another AppDomain
- Next by thread: Re: Urgent. Socket.BeginConnect doesn't work when is called from a separate thread
- Index(es):
Relevant Pages
|
