I have heard people with exactly the opposite problem: Their projects use functionality from many small assemblies and they need the CLR to accept "super modules"-- Managed DLLs containing multiple assemblies.
I would firstly recommend not doing anything, and using profiling and testing to quantify whether you have a problem. Then, the simplest thing is probably to put the forms that are used most often into your code behind assembly's primary module, and put the code for the other forms into non-prime modules. The CLR implements a demand-loading scheme for modules. On the other hand, I understand that modules are only unloaded when AppDomains are unloaded. In your case, this would be when the ASP.NET application restarts. So ultimately, all of the modules will make their way into the working set and just lead to greater overhead. Dominic Cooney -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]] On Behalf Of Bipin Joshi Sent: Saturday, 14 December 2002 9:02 PM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Assembly size and performance In one of the ASP.NET projects I have around 1200 web forms Hello All, In one of the ASP.NET projects I have around 1200 web forms and I anticipate that after final compilation the dll size will be large. I am looking for 'real' information about how size of assembly (dll) affects performance in .NET. Under COM we all know that huge dlls can give trouble when loaded in memory. I searched extensively in various forums but could not get any concrete answer. Any body faced similar problem? -- Regards, Bipin Joshi Microsoft MVP | Developer | Author Looking for .NET information? Must visit www.DotNetBips.com for articles, tutorials, demos and more... -- You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
