>An ASP.NET project can contain several ASPX files. All that is all nice. But, the more files in it, the more the DLL files are bigger. Are there any guidelines on where to cut a project into multiple projects and things like that? By doing that, we have to recreate all the references in the new project so we loose some benefits in there. I would like to know if there are some concerns on having a big DLL file into an ASP.NET application.
The only concern is deployment. The jit compiler will only compile what is needed as it is needed...
Actually, the angry coder wrote an article on this issue with a method to ship a dll for each aspx page, to simplify maintenance. I think it is overkill, but he does make a point if you are using hosting or such it is harder to deploy large dlls.
http://angrycoder.com/article.aspx?cid=5&y=2003&m=4&d=23BOb
