What happens if an application or component is implemented as a single assembly but the components have low cohesion?
In these cases, the development, deployment and support aspects can be negatively affected. This can result in serious deployment problems if parts of the application are modified and new versions of those parts need to be installed. Visual Basic 6.0 supported this type of organization because it allowed the developer to define only a single user class per file. Visual Basic .NET supports having more than one class per assembly, which allows developers to create groups of related classes with high cohesion.
Related Questions
- To apply for both components separate applications must be submitted. Do we download the application twice one for each component titled appropriately, and submit separately?
- What happens if an application or component is implemented as a single assembly but the components have low cohesion?
- What happens if problems arise in the assembly of the lip balms plastic components?
