Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have an ASP.NET project that contains many classes.
I am thinking about creating a class library for the class files so that the code can be reused in other applications. There are two options:
1) Create a class library containing all the classes
2) Create a class library for only the classes that contain code that will be shared and then perhaps use interfaces
Is there any true benefits of option 2? Option 1 would be beneficial because all the code would be in one place.
I would recommend option #2.
If the code will be reused by other applications, I wouldn’t add the additional classes in there, as it would clutter up the library. I would put the remaining classes in the App_Code folder of your ASP.NET application that are specific to that application.