effects of including system assemblies like this

Question

4.00/5 (1 vote)

See more:

C#

using System;
using System.Net;
using System.Windows;
using System.Windows.Controls;
using System.Windows.Documents;
using System.Windows.Ink;
using System.Windows.Input;
using System.Windows.Media;
using System.Windows.Media.Animation;
using System.Windows.Shapes;
using System.Collections.Generic;
using System.Threading;
using System.Windows.Threading;

Will this make the assembly size bigger?

Assuming I'm not using any of the objects from the above namespaces,
Still this has some overhead in my assembly?

Should I ensure I remove all unused namespaces and references in dotnet?

Posted 28-Sep-12 2:14am

Nand32

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

I.explore.code · Answer 1 · 2012-09-28T02:23:00

well, yeah the more assemblies you add/reference the larger the overall assembly grows because they are dlls which are of certain size. Most of the framework dlls would be used from the GAC anyway so they won't be added to your debug folder, only the ones that are either third party or your own would be included in the application (i.e. debug or release) folder.

You can remove the ones that are not being used and that should bring the overall size down but the application would still need some core dlls to work properly like System, System.Windows etc. Hope this helps a bit.