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 was just wondering when is it recommended to make dll’s, when your project is over 1000 lines, 5000lines, more? Also should I make dll’s for WPF controls that WinForm project uses?
Or maybe when the project has reached some number of classes?
Thanks in advance
This is entirely a matter of personal opinion, but if you’re breaking up into projects due to line count or number of classes, you’re doing it wrong. you should have a project (and thus a dll) for every high level logical grouping within your solution. you might have a data project, a domain project… etc. if you’re going to be reusing code across solutions, then yes, you’ll need a dll for that, or a shared project, or something similar.