assemblies

Can I configure a .NET application in a way (settings in Visual Studio) that it references a "local" assembly (not in GAC ) instead of an assembly within the GAC, although both assemblies have the same name and the same version? If both assemblies are strong-named (signed), the CLR will always load from the GAC. Here are the steps the runtime uses to resolve assembly references (from How the Runtime Locates Assemblies ): Determines the correct assembly version by examining applicable configuration files, including the application configuration file, publisher policy file, and machine

Actually i tried to implement some kind of 'statically linked' assemblies, within my solution. So i tried the following: Adding a reference to my assembly with CopyLocal = false Adding the .dll file itself to my solution with 'Add as link' Adding the .dll file itself to my resources with 'Add Resource' - 'Add Existing File' Adding some type out of my assembly into Form1 as private MyObject temp = new MyObject(); After these steps i got the FileNotFoundException as expected. So let's try to load the assembly within the AssemblyResolveEvent with this quick hack AppDomain.CurrentDomain

Just wanted to know if there is any difference between the two, in the context of a fully trust asp.net mvc 2 application. The .NET Framework defers loading assemblies into the current AppDomain until they're needed. For example, if you call into a third-party library only from SomeMethod(), the third-party DLL normally won't be loaded until the first time SomeMethod() runs. AppDomain.GetAssemblies() gives you all assemblies which have already been loaded into the current AppDomain. BuildManager.GetReferencedAssemblies() returns a list of all assemblies referenced from Web.config and elsewhere

Let's suppose I have a Window Forms / Console Application C# project with some external references and references to other class library projects in the same solution too. When I build the Window Form project, I want the referenced libraries be stored in a different location (eg: bin\Release\Libraries ), and not in the same folder as the .exe . Is it possible to do? Alexei Levenkov There are 2 parts of your question: How to configure solutions to build assemblies/EXE into folders of your choice - this is configured through properties of the project in VS (project properties -> build -> output

Does the size of a .net assembly affect performance at all? How about the number of assemblies in your windows forms/web forms project? Dan Blanchard From Microsoft's Patterns & Practices Improving .NET Application Performance and Scalability Chapter 5: Prefer Single Large Assemblies Rather Than Multiple Smaller Assemblies To help reduce your application’s working set, you should prefer single larger assemblies rather than multiple smaller assemblies. If you have several assemblies that are always loaded together, you should combine them and create a single assembly. The overhead associated