There are usually some that I don’t use in whatever project I’m working on (System.XML, System.XML.Linq for example).
Are there any drawbacks from leaving default assemblies that I won’t be using in my project?
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.
There are usually some that I don’t use in whatever project I’m working on (System.XML, System.XML.Linq for example).
Are there any drawbacks from leaving default assemblies that I won’t be using in my project?
Unused referenced assemblies are removed by the compiler.
Create a new console app in VS and it will default reference inn several assemblies. Compile your empty program and open it in reflector, and you’ll see that only mscorlib is referenced. The others are removed.
Same goes for unused
usingstatements. The compiler removes them.You might want to remove unused references and using for the sake of keeping things clean and more readable.