I have a sample ASP.NET application. The appliaction was developed as POC and not following any design and architectural standards.
Now I want to restructure the application. I can see some of the business logic and controls can be reused in future, such as login control.
I have two options for restructuring
-
I create a Utility DLL that will contain all such resusable code and another DLL that will contain all controls that can be reused.
-
I will create a separeate DLL for each type which can be reused e.g. Login control.
Which option is more better. Although I feel option 1 is good, but I need suggestion from experts.
I have no idea why you would want to keep a separate assembly per type. Don’t do that.
Keep related functionality together in a single assembly. Look at how the .NET Framework is organized for examples. Note how, if you’re not doing data access, you don’t need to reference
System.Data.dll.