Use Project (*. csproj) in the. NET/C # project to organizeCodeIt has several advantages over organizing folders in the same project:
- From the perspective of the customer code, I rely on a few things from you, you can only rely on this things (made into a separate project), do not need to rely on other irrelevant code
- From the perspective of access control and visibility, the internal keyword of C # is for the physical module, that is, the DLL, rather than the namespace or folder.
- To avoid bidirectional dependency, Visual Studio blocks bidirectional dependencies between two projects, but does not block dependencies between different folders or namespaces in the same project.
- From the deployment perspective, the deployment unit is DLL. If you need separate deployment and flexible deployment, the DLL should be a single cohesive function module, the folder or namespace is not physically matched after compilation
Do you have other considerations? How do I feel that. Net/C # does not support code design and deployment?
