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’m using c#. In many cases I’m writing code that can benefit from a very simple class/method located in a “non-relevant” dll. For example, I’m writing some algorithm with no UI but it can benefit from a Point class in System.Drawing, or I need some xml manipulation method from System.Web even though I’m writing a console app (these are just examples).
Besides the “code smell” – is there a performance penalty for importing a big assembly for a small chunk of functionality?
Yes, there is a performance penalty associated with loading assemblies (e.g. loading assemblies require verification and occupies address space from your process), but it may not be significant, so you should check how it affects your application. Most likely it will not be a big issue.