6. Static/Dynamic Ref., Assembly.Load(), Assembly Qualified Name

16. Is using Assembly.Load() a static reference or dynamic reference?
Dynamic references are constructed on the fly as a result of calling various methods, such as System.Reflection.Assembly.Load. The preferred way to reference an assembly is to use a full reference, including the assembly name, version, culture, and public key token if one exists. The runtime uses this information to locate the assembly. The runtime uses the same resolution process regardless of whether the reference is for a static or dynamic assembly.

17. When would using Assembly.LoadFrom(), Assembly.LoadFile() be appropriate? Assembly.LoadFrom() loads an assembly given its file name or path. Assembly.LoadFile() loads the contents of an assembly file on a specified path, loading the assembly into the domain of the caller. Such as a plugin…

18. What is an Assembly Qualified Name? Is it a filename? How is it different? An assembly’s name is stored in metadata and has significant impact on the assembly’s scope and use by an application. A strong-named assembly has a fully qualified name that includes the assembly’s name, culture, public key and version number. It allows versioning and signing compared to a filename.

Happy Programing! =)

Source: MSDN, Ctrl+Alt+J the good old friend the Object Browser.