Load(AssemblyName)

Assembly.Load() vs. LoadFrom()

Commonality — Tue, 05 Oct 2004 03:24:00 GMT

Jon Flanders posts here about a problem he diagnosed recently about Assembly.LoadFrom() and Assembly.Load() behaving differently. The issue he basically...

re: Load(AssemblyName)

Terry Massey — Fri, 13 May 2005 08:11:13 GMT

It is nice to finaly see who deals with by far my favorate thing in .net. The Assymbly.Load function is by far one of the best ways to dynamicly load modular/Componentized applications. I use this function extensivly with most of my projects, especialy when I need to run CRON or scheduled tasks. I have writen many a task manager where I take and I guess after waching the Channel 9 stuff is a bad thing to do but reading a folder that I place my dll's/Asymblies in for dynamic loading of my jobs. I is nice to be able to load up an asymbliy with out having to register it like in COM or in the GAC.

I should really spell check this but hey it is a blog and I am a developer.

re: Load(AssemblyName)

Jejo — Thu, 13 Oct 2005 14:55:36 GMT

Hi. I'm trying to dynamically load/unload assemblies, as I am compiling them at runtime. Every time I compile a new version, I'd like to switch the assemblies. Is there some kind of workaround so that this is possible?

I tried to load every assembly in a separate AppDomain, so I can do an .UnLoad on it, destroying all the loaded assemblies within.

Another approach would be to run assemblies side-by-side based upon version info & strong names. I did not yet delve into that one.

Now I've just read that assemblies used from other appdomains get loaded into the consuming appdomain, so the solution I depicted above only results in the same blocking situation.

Maybe this is an egghead idea, maybe not. But it would be REAL nice to get some kind of dynamic unloading to work. After all, constantly loading new assemblies would be unnessecary memory usage.

re: Load(AssemblyName)

IcingDeath — Thu, 03 Nov 2005 20:26:24 GMT

This goes for Load(),LoadFrom() and LoadFile() [duh!].
When I have an executable trying to load Dll file X with dependency Y, the dll will fail to load unless y is located in the same path with the executable and not in the same path with the dll.
Am i making any sense??? Is this the expected behavior? What happens if I wanna load a plugin with dependencies (other than the ones located in the GAC) and they are located in the same path with the DLL but not in the path of the .exe??
Maybe this is a bug? Framework 1.1

re: Load(AssemblyName)

Seshagiri — Fri, 02 Mar 2007 22:45:31 GMT

A majority of my applications/ libs are weakly named assemblies (I have no reason to make them strongly named).

If I want to load these dynamically, what is the best method to use:

Assembly.LoadFrom (or) Assembly.Load()?

thanks

Sesh

re: Load(AssemblyName)

Hamid — Sun, 11 Mar 2007 21:10:58 GMT

Hi,

would you please help me?

i wanna set transparent swf file in my form. i did add axshockwave and set swf file with it, but it dose not in transparent mode :-(

i will many thank you if you help me

good luck

re: Load(AssemblyName)

Fernando Simonazzi — Thu, 20 Sep 2007 04:47:18 GMT

Hi,

By "If the CodeBase is set, but the Name is not, however, then it's the same as calling Assembly.LoadFrom() on that CodeBase.", do you also mean that the assembly will be loaded in the LoadFrom context?

Thanks!

Fernando