> Hi,
>
> I have a scenario where AppDomain.CurrentDomain.GetAssemblies () only
> return
> part of the loaded assemblies in that AppDomain. I know it is not
> complete,
> because the code doing this call is located in assembly B, which is called
> from assembly A, and in the result of GetAssemblies I do get B, but not A,
> which is obviously incorrect.
>
> Is this a known issue? Any workaround? I don't have a reproducible test as
> it happens on our CodeDom provider under IIS on Windows Server 2003 with
> SP 1
> when we touch the machine config.
>
> Thanks,
> Manu
>
> --
> ---------------------------------------------------------
> Eiffel Software
> http://www.eiffel.com
> User group: http://groups.eiffel.com/join
> ---------------------------------------------------------

>> What exactly do you mean with "touch the web config", do you mean you
>> change
>> it's contents while your application is running? Note that asp.net will
>> unload the AD when you do this.
>
> That's correct, IIS is running and I'm just saving the web config, then I
> try to access one of my ASP.NET pages and this is where the problem lies.
>
>> Did you try to attach the debugger while this happens, that way you can
>> check where the assemblies are loaded. Could it be that some assemblies
>> are
>> loaded domain neutral?
>
> Yes, I did attach the debugger and it shows that all my assemblies are
> loaded in the new AppDomain created by ASP.NET, however GetAssemblies does
> not show all the one the debugger shows.
>

> What exactly do you mean with "touch the web config", do you mean you change
> it's contents while your application is running? Note that asp.net will
> unload the AD when you do this.

> Did you try to attach the debugger while this happens, that way you can
> check where the assemblies are loaded. Could it be that some assemblies are
> loaded domain neutral?

> The transition between the two assemblies is not done through AppDomain, I
> can guarantee this because my code is not creating AppDomain. As pointed
> out
> in my original post, the issue arises in IIS with ASP.NET which creates
> AppDomain.
>
> I forgot to mention that I'm using .NET 1.1 on the Windows 2003 Server
> with
> SP1 and this happens not when touching the machine config, but on the web
> config for my test website.
>
> Regards,
> Manu
>
> --
> ---------------------------------------------------------
> Eiffel Software
> http://www.eiffel.com
> User group: http://groups.eiffel.com/join
> ---------------------------------------------------------
>
>
> "Willy Denoyette [MVP]" wrote:
>
>> And what if B is not loaded in the same AD as A?
>>
>> Willy.
>>
>> "Emmanuel Stapf [ES]" <EmmanuelStapfES@discussions.microsoft.com> wrote
>> in
>> message news:35D14887-6188-4784-93CE-42DD999A932E@microsoft.com...
>> > Hi,
>> >
>> > I have a scenario where AppDomain.CurrentDomain.GetAssemblies () only
>> > return
>> > part of the loaded assemblies in that AppDomain. I know it is not
>> > complete,
>> > because the code doing this call is located in assembly B, which is
>> > called
>> > from assembly A, and in the result of GetAssemblies I do get B, but not
>> > A,
>> > which is obviously incorrect.
>> >
>> > Is this a known issue? Any workaround? I don't have a reproducible test
>> > as
>> > it happens on our CodeDom provider under IIS on Windows Server 2003
>> > with
>> > SP 1
>> > when we touch the machine config.
>> >
>> > Thanks,
>> > Manu
>> >
>> > --
>> > ---------------------------------------------------------
>> > Eiffel Software
>> > http://www.eiffel.com
>> > User group: http://groups.eiffel.com/join
>> > ---------------------------------------------------------
>>
>>
>>