title: oData client limit classes
body: <p>I am currently testing oData client in combination with Dynamics AX 7. The metadata file coming from AX is over 900'000 lines big and if i use the default oData client and auto generate a C# class file it won't build because of too many string literals (.net error). </p>
  
  <p>Now i'm looking for a way to tell the client generator which classes to generate (by entity name for example) and which not (about 95% isn't needed on the client-side).</p>
  
  <p>Sadly limiting the metadata on AX side is not an option.</p>