"Vagif Abilov" <vagif@online.no> wrote in message
news:OmJYrHMXFHA.2348@TK2MSFTNGP14.phx.gbl...
> Hello,
>
> 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.
>
> It looks like not much can be done about it, because probing path can only
> be extended with sub-directories of the base directory, and the new domain
> simply does not have access to assemblies available to a domain-creator,
> unless they are installed in the GAC.
>
> Right now to resolve this issue I temporary copy missing assemblies to a
> new domain base directory, but such approach is quite ugly.
>
> Am I overlooking something? Is this by design, and if I create a new
> domain with its own base directory, it can't search for required
> assemblies in the directory of the creating domain?
>
> Thanks in advance
>
> Vagif Abilov
>

"Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
news:urH7P7MXFHA.1148@tk2msftngp13.phx.gbl...
> See if the AppDomain.AssemblyResolve event is your friend.
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Vagif Abilov" <vagif@online.no> wrote in message
> news:OmJYrHMXFHA.2348@TK2MSFTNGP14.phx.gbl...
>> Hello,
>>
>> 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.
>>
>> It looks like not much can be done about it, because probing path can
>> only be extended with sub-directories of the base directory, and the new
>> domain simply does not have access to assemblies available to a
>> domain-creator, unless they are installed in the GAC.
>>
>> Right now to resolve this issue I temporary copy missing assemblies to a
>> new domain base directory, but such approach is quite ugly.
>>
>> Am I overlooking something? Is this by design, and if I create a new
>> domain with its own base directory, it can't search for required
>> assemblies in the directory of the creating domain?
>>
>> Thanks in advance
>>
>> Vagif Abilov
>>
>
>

"Gunter Prossliner" <gpointprossliner@removegmx.at> wrote in message
news:A161CD49-3BA7-4452-8EDB-0F9782535B63@microsoft.com...
> 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

> 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.