Assembly Sharing

Question

A have a design question. I wrote a couple of C # applications. Most of these applications have their own sql or access database, but then they also use a common database, but they are completely different applications that have their own responsibilities in their own business domains.

Some people I spoke to believe in the following: Applications must be silos. They should not separate anything. No sharing of assemblies, components, or databases.

I need some advice on this. When it is acceptable to share, or it is never a good idea.

thank

Answer 1

, -... , , , .

, , (.. "" ), ( ). , Project Project Project B, , Project B Project A, . SOA; - WCF, public mex/wsdl API ( ).

, , .

Answer 2

, "dll"? ...

, ?

Answer 3

, .

, , . , , , , , "t " ".

, , - , .NET. , , .

, , . , , , , , , . , , , .

Answer 4

( , .) - , . : , ( ), , , . , .

Answer 5

dll - , . , , .

. , , , . dll hell. .NET - DLL - . , , DLL.

. , .

EDIT:

If you mean teams working in silos and not sharing the code, then Dr. Jokepu is right: joint development of efforts between individuals and teams is a definite “necessity”.

Answer 6

Sharing assemblies in applications makes sense only from a theoretical point of view. In practice, this brings a whole bunch of problems. Avoid sharing assemblies; locally host all assemblies.