Just like Carl’s question over here I would like to ask you (because I couldn’t find it out on my own 🙁 ) if there is any benefit by removing an assembly reference that is not statically nor dynamically (via reflection for example) used.
Share
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.
Removing unused assembly references wouldn’t change anything apart from cleaning your projects. When you add assembly references the compiler will ignore any assembly which you have not actually made use of in your code. Thus, if you were to set a reference to System.Data.dll and System.Windows.Forms.dll but only authored the following code:
the compiler would only reference the mandatory mscorlib.dll