Question: Good programming practice these days tends to mean splitting your stuff up into lots of assemblies and namespaces (for example, see [S#arp Architecture](http://www.sharparchitecture.net/), [MVC](http://www.asp.net/mvc), etc.). However a side-effect of that is that you have to stick a whole bunch of 'using ' directives into every class file. You know the sort of thing: Every controller class needs to 'use' the models and viewmodels namespaces, etc., etc.

Are there any techniques for making this easier? For example, is it possible to declare `using` directives at the namespace level instead of the file level - so that every class in a namespace 'foo' automatically is using namespace 'bar'? Or are there smart ways of setting the default 'usings' that Visual Studio adds, based on the folder you are in? Or other ways of making the adding of 'usings' less tedious?

Answer: 
As discussed in [this question](https://stackoverflow.com/q/5008991/590790), this is not possible.

When you have long lists of usings, you possibly are also having too much dependencies. It might be an indication that you need to do some refactoring.
As far as the language goes, there is nothing like what you're after.

The best option you have is to use tools (like some of those in Visual Studio) that allow you to add usings automatically for a selected "unknown symbol", sort usings alphabetically, or strip usings that are no longer required in the current file.