J
Joe Duchtel
Hello -
I am using the AppDomain.CreateDomain() function to load an assembly
from a local *.dll where the *.dll is also in the GAC. This worked
fine for .NET 1.1 where it would load the local file but with .NET 2.0
(Visual Studio 2008) it always loads the version in the GAC instead.
I changed the CreateDomain() as follows to tell it that I want to use
the X.dll from C:\Test and NOT the GAC ...
mAppDomain = AppDomain.CreateDomain("C:\Test\X.dll", Nothing, "C:
\Test", Nothing, False)
.... but it keeps loading the version from the GAC. I also looked into
using the AppDomainSetup but I'm not sure which settings to specify in
there. I'd like to keep it simple ... just ignore the GAC ...
I am launching the application that calls CreateDomain() via the
Debugger (Start external program) when I debug X.dll. Is there a lock
on the local X.dll because of that? This used to work fine in Visual
Studio 2003 ...
Thanks,
Joe
I am using the AppDomain.CreateDomain() function to load an assembly
from a local *.dll where the *.dll is also in the GAC. This worked
fine for .NET 1.1 where it would load the local file but with .NET 2.0
(Visual Studio 2008) it always loads the version in the GAC instead.
I changed the CreateDomain() as follows to tell it that I want to use
the X.dll from C:\Test and NOT the GAC ...
mAppDomain = AppDomain.CreateDomain("C:\Test\X.dll", Nothing, "C:
\Test", Nothing, False)
.... but it keeps loading the version from the GAC. I also looked into
using the AppDomainSetup but I'm not sure which settings to specify in
there. I'd like to keep it simple ... just ignore the GAC ...
I am launching the application that calls CreateDomain() via the
Debugger (Start external program) when I debug X.dll. Is there a lock
on the local X.dll because of that? This used to work fine in Visual
Studio 2003 ...
Thanks,
Joe