CODEWITHSUNDEEP
.netdll
Tauseef
Tauseef

Reputation: 424

What is the best way to manage dll libraries?

I am having difficulties to manage all the dlls used in different projects. we have like 15 different application running in our company and they are pointing to different libraries.

Now we are converting all these asp.net applications + Libraries to .NET 4.0 and possibly rewriting some libraries with Entity Framework.

I am wondering what is the best way to organize these libraries?

  1. Should we create one solution, categories the libraries into different projects and add those project into one solution?

  2. Should we create one project and categorize the libraries into different folders and build as one library?

if we use the 2nd approach would it be any performance issue? What is the most efficient approach performance wise?

Upvotes: 1

Views: 957

Answers (2)

GameAlchemist
GameAlchemist

Reputation: 19294

I am surprised the word 'NameSpace' didn't pop-up in your question, because it is one good way to put order in your code if you have a great number of Class / enum / modules / ... Personnaly i do use NameSpaces (and i nest them sometimes), which allows me to avoid some name conflict issues, and permit also a more convenient use of intellisense.

Upvotes: 0

jgauffin
jgauffin

Reputation: 101192

For all libraries that are shared between multiple applications:

  • Group the related libraries together in an own solution. Which means that you'll get one or solutions for the libraries only.

  • Then use an own nuget hosted service to handle the dependencies. By doing so you can easy manage dependencies in your applications. Its just a question of invoking "update-package" in the package manager console.

By using nuget you can also include templates and such showing how to use each library and automatically modify app/web.config to add the required keys.

Upvotes: 2

Related Questions