title: Best practices: C# Extension methods namespace and promoting extension methods
body: <p>I know there exists already a <a href="https://stackoverflow.com/questions/1051066/naming-conventions-for-extension-method-namespaces-and-sponsor-classes">post</a>, describing nearly the same, but I think mine is a bit different.</p>
  
  <p>What I would like to know is how you organize your extension methods in terms of assigning the namespace. Currently - for the extension methods in our framework - I use the following namespace pattern</p>
  
  <ul>
  <li>MyCompany.Web.Utils</li>
  </ul>
  
  <p>and inside I have the extension method classes. This is fine for me with the disadvantage that the extenders are not immediately visible to our software developers. Consider the case where I have a StringExtender class which provides a quite handy <a href="http://blog.js-development.com/2008/12/using-extenders-to-abstract-details-and.html" rel="noreferrer">extension method "In"</a> that extends the <code>String</code> object. Having the extension method withing the above mentioned namespace, our programmers won't see the extension method unless they explicitly include its namespace. Instead, if I would put the extension method in the <code>System</code> namespace, everyone would immediately see it, but I've <a href="https://stackoverflow.com/questions/321921/is-it-ok-to-write-my-own-extension-methods-in-the-system-namespace">read that this is bad practice</a>.</p>
  
  <p>So my question is how you do promote your extension methods s.t. they are used by your developers.</p>