I imagine a single DLL could be quite large and not cause problems. If you are finding that you have that much code in a single project, it's not a bad idea to break it apart. Compartmentalize your code. You could create a project that handles all your data tasks (talking to the database) in a separate project. A quick look at the runtime dlls show this:
Code:
77,824 System.Configuration.Install.dll
1,290,240 System.Data.dll
299,008 System.Data.OracleClient.dll
1,699,840 System.Design.dll
86,016 System.DirectoryServices.dll
1,216,512 System.dll
65,536 System.Drawing.Design.dll
466,944 System.Drawing.dll
241,664 System.EnterpriseServices.dll
64,000 System.EnterpriseServices.Thunk.dll
368,640 System.Management.dll
241,664 System.Messaging.dll
323,584 System.Runtime.Remoting.dll
131,072 System.Runtime.Serialization.Formatters.Soap.dll
77,824 System.Security.dll
126,976 System.ServiceProcess.dll
1,245,184 System.Web.dll
819,200 System.Web.Mobile.dll
57,344 System.Web.RegularExpressions.dll
569,344 System.Web.Services.dll
2,039,808 System.Windows.Forms.dll
1,335,296 System.XML.dll
You have to write a lot of code to get up to a 2 meg DLL.
Peter
------------------------------------------------------
Work smarter, not harder.
.dll file
