Reflection

Brief Difference
You should never use Assembly.LoadFile(). Use LoadFrom() if you know where the assembly is located, use Load() to let .NET figure out where the assembly is located. Using Load() should be your preference but may require a .config file to help .NET find the assembly like below










Differentiate LoadFrom and LoadFile

Use the LoadFile method to load and examine assemblies that have the same identity, but are located in different paths. LoadFile does not load files into the LoadFrom context, and does not resolve dependencies using the load path, as the LoadFrom method does. LoadFile is useful in this limited scenario because LoadFrom cannot be used to load assemblies that have the same identities but different paths; it will load only the first such assembly.

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Crish16y ago
pl go through below links..

http://www.proprofs.com/forums/index.php?showtopic=13287

http://msdn.microsoft.com/en-us/library/b61s44e8.aspx

will helpful for you.
Vipul Kelkar16y ago
thanks jaish..it was helpful
Jaish Mathews16y ago
Brief Difference
You should never use Assembly.LoadFile(). Use LoadFrom() if you know where the assembly is located, use Load() to let .NET figure out where the assembly is located. Using Load() should be your preference but may require a .config file to help .NET find the assembly like below










Differentiate LoadFrom and LoadFile
Use the LoadFile method to load and examine assemblies that have the same identity, but are located in different paths. LoadFile does not load files into the LoadFrom context, and does not resolve dependencies using the load path, as the LoadFrom method does. LoadFile is useful in this limited scenario because LoadFrom cannot be used to load assemblies that have the same identities but different paths; it will load only the first such assembly.