title: Alternative to libraries of static classes
body: <p>I have a large collection of static 'Utility' classes that contain very generic static methods. For example, I have a CollectionUtility class that has useful methods like:</p>
  
  <p>public static void RemoveDuplicates(ICollection collection)... etc</p>
  
  <p>With C# 3.0 I've been converting these to extension methods.</p>
  
  <p>Now, I've heard some talk that in an 'enterprise level' application it is often considered best practice to avoid large libraries of these static classes and methods. I imagine that it could get quite hard to maintain.</p>
  
  <p>A question for those of you who work on large enterprise projects for large companies - do you maintain libraries of utility classes like these or not? What do you?</p>