Once the AppDomain is created and has performed it's first bind you
can't set that property any more. You can set private paths, but they
have to point into some directory underneath ApplicationBase.
Also note that SetupInformation will always return a clone of the actual
AppDomainSetup object, and never return the actual one being used.

Signature
Justin Rogers
DigiTec Web Consultants, LLC.
Blog: http://weblogs.asp.net/justin_rogers
> In microsoft articules the say that Assembly load method is the one that is
> used by the clr to locate and load an assembly. They discriped in create
[quoted text clipped - 16 lines]
>
> Assembly Asm1 = currentDomain.Load("assembly.dll");
Roger Tan [MSFT] - 22 Jun 2004 20:46 GMT
To further explain what Justin described, you will need to create a new
AppDomain (and not use the current appdomain). You can instantiate a new
AppDomainSetup object, and set the AppBase appropriately. Then, create a
new AppDomain with the new AppDomainSetup object, and things should work
fine.