Nicola Cisternino wrote:
> Sorry,
> double post ! ....
>
> Nicola Cisternino wrote:
>
>> Hi all,
>> I've developed a custom control that uses a public interface and can
>> be plugged using external assemblies that implements this interface.
>> The assembly, therefor, must be loaded dynamically using reflection
>> (Reflection.Assembly.LoadFrom("<assemblyname")).
>> Now, all works fine at run time but at design time a
>> FileNotFoundException exception is raised, ergo: the assembly is
>> missing ...
>> How i can load the assembly both at design and run time (I'm using
>> .NET 1.1) ?
>> I've already tried put to the assembly into the "PublicAssemblies"
>> folder .... without results :-(
>> It's very strange... i've also tried to load the assembly using the
>> complete static path (C:\bla\bla\bla\assembly.dll ....) .... but at
>> design time occurs the usual exception ...
>>
>> Any idea ?
>> Thanks.
>> Nicola.

Petar Repac wrote:
> Nicola Cisternino wrote:
>
>> Sorry,
>> double post ! ....
>>
>> Nicola Cisternino wrote:
>>
>>> Hi all,
>>> I've developed a custom control that uses a public interface and can
>>> be plugged using external assemblies that implements this interface.
>>> The assembly, therefor, must be loaded dynamically using reflection
>>> (Reflection.Assembly.LoadFrom("<assemblyname")).
>>> Now, all works fine at run time but at design time a
>>> FileNotFoundException exception is raised, ergo: the assembly is
>>> missing ...
>>> How i can load the assembly both at design and run time (I'm using
>>> .NET 1.1) ?
>>> I've already tried put to the assembly into the "PublicAssemblies"
>>> folder .... without results :-(
>>> It's very strange... i've also tried to load the assembly using the
>>> complete static path (C:\bla\bla\bla\assembly.dll ....) .... but at
>>> design time occurs the usual exception ...
>>>
>>> Any idea ?
>>> Thanks.
>>> Nicola.
>
>
> The subsystem of .net that is responsible for loading asssemblies
> is called Fusion.
> It can be configured in registry, think the location is
> HKLM\Software\Microsoft\Fusion
>
> You can configure it to log successful and unsucessful assembly loads
> in some folder and there see what assemblies was loaded and where .net
> was trying to found them.
>
> Petar