You can partially disregard my last email (the part about the fusion log,
you won't need it) I didn't actually thoroughly read your code :)
Your code below causes the Assembly to load in both AppDomains. The
"secondDomain.Load" loads it into the second AppDomain and your reference
causes it to loa
Pretty sure there's nothing you can do in this regard when you are missing
dependencies that are required to load the assembly (assembly-level
Attributes, base classes, etc must all be loaded to load the metadata for an
assembly -- note that this does not include dependencies that are only
inside m
On 11/8/07, Graeme Taylor <[EMAIL PROTECTED]> wrote:
>
> Lol - nothing I like for than some light bedtime reading :o|
Well, the beauty of the internet is that someone somewhere has probably
already implemented this kind of code and made it freely available for
reuse. Like the people at http://ww
Lol - nothing I like for than some light bedtime reading :o|
As a temporary workaround, I've copied all dependencies to the directory -
still get a FileNotFound.
The parameter being passed in is
@"c:\mySupportApp\staging\myApp.Plugins.Email.dll"
Code is:
private List GetTypesFromAssembl
On 11/8/07, Graeme Taylor <[EMAIL PROTECTED]> wrote:
>
>
> Is there no way round this? I have no interest in finding out methods or
> trying to run anything from this assembly.
Sounds like someone may be spending some quality time with the CLR file
spec... :)
--
Curt Hagenlocher
[EMAIL PROTECTE
Hi Adam,
Thanks for your input. You are correct - I do a get a FileNotFound as the
dependencies are missing.
Is there no way round this? I have no interest in finding out methods or
trying to run anything from this assembly.
Graeme
===
This list is hosted by De
Whoops, nix the AssemblyName note since that's only applicable to
Assembly.Load.
Setting the ApplicationBase property of the AppDomainSetup you can pass to
create an AppDomain should work.
-Original Message-
From: Adam Sills [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:3
You can always override the codebase of an AppDomain you're creating to be
the location of the plugin DLL.
You can also use ReflectionOnlyLoad if you pass an AssemblyName object,
which can be retrieved via AssemblyName.GetAssemblyName( string assemblyPath
) which sets the codebase for your loaded
Hi,
I would like to get a list of public types that are in an assembly. The
complicating factor is that I do not wish to load the assembly into my
AppDomain as I will never execute it.
I cannot use Assembly.ReflectionOnlyLoadFrom(...) as the dependencies will
not be available.
I thought about l
