Disadvantages and Advantages of separated projects/DLLs in .NET? How many of them are too much? -


Some other related questions are included in the question, I will throw each one of them one or many Li> What are the benefits of separating projects / DLLs?

  • What are the disadvantages of separating projects / DLLs?
  • If I have a new solution / DLL for every shareable resource, there are not many projects going on?
  • After too many projects (like 40+) this IDE functionality (VSNET) 2008)?
  • I am asking this question because I have found this big solution with so many different sections and now I need to separate some interfaces, all of which are different ( circular dependence problem) and now I need to make several DLLs, I just want to do it right now. The answer to this question can be very long in relation to the region o Argument of argument, I think:

    First of all, it would be better to note whether there are reasons for selection and separation of items in many assemblies, and in general it can be in general design and layering and / or project structure To clean

    What are the benefits of separating 1 solution / DLL?

    The advantage of separation of solutions and assemblies is related to a design approach, a code reuse and layers organization, as stated, helps to separate the solution objects / To share components and distribute responsiveness between the layers, encourage multi-goal and pluggable solutions (for example, various storage target assembly (database, files, etc.), testability

    2 What are the disadvantages of separation of Solution / DLL?

    Major losses, as previously stated to me, firstly, all the complications (management, maintenance), performance (but this is the second discussion, it is not easy to say that )

    3 If I make a new solution / DLL for every shareable resource, then there are not many solutions being solved?

    It depends, first of all, I think this design may depend on the choice

    4 lots of solutions (like 40+) Is it going to have some bad effects on IDE functionality (VSNET 2008) later?

    I am not sure about the decline in execution in the VS 2008 IDE, but it can definitely influence the performance to manage a solution of 60+ projects, for example For 4 projects with 4 solutions each .. It should be clear that the display of VS IDE can be degraded even after opening 35 files simultaneously, or double project solution In the end, I think Big Thang I have to mind that for example in the over-design fall in fact it is really necessary to "build" it is better, therefore

    It became very difficult to manage things very complex (for many projects) and to stop it and think "everything is going well?"

    Comments

    Popular posts from this blog

    python - Overriding the save method in Django ModelForm -

    html - CSS autoheight, but fit content to height of div -

    qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -