Here's a great application with many sub-applications (500 + DLL) at work
Working with all these DLSs and dependencies as a developer is very disappointing. You create a new project and add 5+ DLLs to get the system's main pieces (logging, auditing, security, messaging ect). Every new subpage we add, we make any other projects necessary to share things between a web project, a business layer, data layer and 3, so our list is expanded.
My question is, what is the best way to manage it? I do not think what's best .. Modular approach looks good for the utility again, and hot patching items without taking down the system for an application. But headache in the management of 500 DLS is a nightmare.
Does each subsystem actually require 3-4 projects, and other 5 core pieces are referred?
What are other ways to make big arrangements in keeping with the projects / keeping the development and deployment?
I have a very good experience with all kinds of naming guidelines (currently I am 250+ DLS I am working on the project) If you (or any other) choose good naming conventions, then first you see what is "this" and you know how much the name is.
Do not worry about counting references in the project. If you are disappointed with adding X references every time, you can create a macro that will do it instead of you. Or you can use a template VS with your specific requirements. You can create solutions / projects / items (files).
Large projects are big, so it's not surprising if you have a large amount of DLL, classes, etc ..
Comments
Post a Comment