assemblies

In some C# code I have taken over (in Visual Studio 2005), I have noticed that the assemblies are all signed with the same .snk file. Why would the previous author have signed the assemblies in this way? Is signing assemblies necessary and what would be wrong with not signing? What disadvantages are there in signing assemblies - does it cause delays? Why would the previous author have signed the assemblies in this way? No idea, maybe he wanted all his assemblies to be signed with the same key. Is signing assemblies necessary and what would be wrong with not signing it? No, it is not necessary

I have a assembly. In this assembly I have a class and interface. I need to load this assembly at runtime and want to create an object of the class and also want to use the interface. Assembly MyDALL = Assembly.Load("DALL"); // DALL is name of my dll Type MyLoadClass = MyDALL.GetType("DALL.LoadClass"); // LoadClass is my class object obj = Activator.CreateInstance(MyLoadClass); This is my code. How could it be improved? If your assembly is in GAC or bin use the assembly name at the end of type name instead of Assembly.Load() . object obj = Activator.CreateInstance(Type.GetType("DALL.LoadClass,

From the command line (or by any means really), how can I determine which CLR version a .NET assembly requires? I need to determine if an assembly requires 2.0 or 4.0 CLR version. ildasm.exe will show it if you double-click on "MANIFEST" and look for "Metadata version". By default, it's the version that the image was compiled against. Fernando Gonzalez Sanchez One clarification... The problem with all the mentioned methods is that they will return version 4.0 if assembly was compiled against .NET framework 4.0, 4.5 or 4.5.1. The way to figure out this version programmatically at runtime is