Home/ Questions/Q 101063
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T00:41:56+00:00

For example: using System; using System.Web; using System.Collections; using System.Web.Services; using System.Web.Services.Protocols; using System.Web.Script.Serialization;

  • 0

For example:

using System; using System.Web; using System.Collections; using System.Web.Services; using System.Web.Services.Protocols; using System.Web.Script.Serialization; using System.Web.Script.Services; using System.Web.Security; using System.Data; using System.IO; using System.Net; using System.Text; using System.Xml; using System.Xml.XPath;  using System.Web.Configuration; using System.Collections.Generic;

I have something like that in a class that I have inherited. I could remove each namespace one by one to see if the class builds, BUT does it matter?

If I am not sure if System.Xml is needed, should I remove it?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. In general all they do is add clutter.

    However, they can in some specific circumstances cause problems with duplicate names in scope, or duplicate extension methods. For example, if there are classes Foo.SomeType and Bar.SomeType, and you have using Foo; and using Bar;, then references to SomeType will need disambiguating. The extension methods work similarly where static classes in different namespaces contribute conflicting extension methods.

    The VS2008 tools (including express) include options to remove unnecessary using statements, which is very useful for tidying the code.

    • 0