When do we need to put using directives inside a namespace scope?

Question

I don't know why Asp.net MVC developers put the using directives inside System.Web.Mvc namespace as follows.

namespace System.Web.Mvc
{
    using System;
    using System.Collections.ObjectModel;

    [Serializable]
    public class ModelErrorCollection : Collection<ModelError>
    {

        public void Add(Exception exception)
        {
            Add(new ModelError(exception));
        }

        public void Add(string errorMessage)
        {
            Add(new ModelError(errorMessage));
        }
    }
}

When do we need to put using directives inside a namespace scope?

I don't know if it's even necessary. The only reason I could think of that might require that is if you have a source file that has multiple namespaces within it. But how often to people _really_ do that? Not a lot I hope. — Jeff Mercado, Feb 17 '11 at 05:59

score 3 · Accepted Answer · edited May 23 '17 at 12:13

3

See Should 'using' statements be inside or outside the namespace?

edited May 23 '17 at 12:13

Community

1
1

answered Feb 17 '11 at 06:01

C.Evenhuis

25,996
2
58
72

score 2 · Answer 2 · edited May 23 '17 at 12:20

2

It's your choice. StyleCop tool warns of it as a best practice, however Visual Studio generated files always have usings outside namespace.

Should all the using directives for namespaces be inside the namespace?

edited May 23 '17 at 12:20

Community

1
1

answered Feb 17 '11 at 06:01

Artem Koshelev

10,548
4
36
68

When do we need to put using directives inside a namespace scope?

2 Answers2