Re: Appending to CurrentDomain private path using AppDomainSetup

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: rlander [MSFT] (rlander_at_microsoft.com)
Date: 12/18/04 

Date: 17 Dec 2004 16:43:41 -0800

I hear you ... I've got a couple questions for you to help me
understand your scenario:

1. Do the assemblies in these private paths have unique dependent
assemblies or is there some overlap?
2. Why can you not determine all of the private paths at appdomain
creation-time, or are you using the default domain?
3. If you are using the default domain, can you add these private paths
to your config file?

I really want to understand scenarios where you really do find out
about these private paths as you go and cannot know them up front. We
have to ensure that future versions of the Framework accomodate these
scenarios.

I certainly agree that Assembly.Load is the way to go. You avoid issues
that come along with other Loader APIs ...

thanks -- rich

Relevant Pages

  • ILMerge
    ... shifting towards being in favor of it in some scenarios. ... Typically you have to drag around the corresponding interop ... assemblies along with the primary assembly. ... ILMerge solves that nicely. ...
    (microsoft.public.dotnet.general)
  • Re: ASP .NET 2.0 Unanswered questions...
    ... Yes, this would be in scenarios where you just deploy your pages, ... multiple assemblies. ... application-the Global Assembly Cache, the Bin subfolder, and the ... the language set on the .aspx page), and compiles it on the fly. ...
    (microsoft.public.dotnet.framework.aspnet)