title: Web API - Architectural Design
body: <p>i have a design question regarding a Web API infrastructure solution.</p>
  
  <p>I have the following use case scenario:</p>
  
  <ol>
  <li>A Dynamic Web Form Generator which produces an XML Configuration File where i have all necessary information regarding DB, Connection, Table Name, Fields....</li>
  <li>A Web based Client which includes/creates a Web Form out of the XML Configuration file as an extension</li>
  <li>Generic .NET Web API HTTP Service Layer which handles the Interaction Client/Server with generic CRUD operations</li>
  </ol>
  
  <p>My question:</p>
  
  <ul>
  <li>Which would be the best approach to build a generic Web API, taking in account that the structure from webform to webform (DB, fields, tables, types) can be different.....</li>
  <li>Is it possible to create the Model Class at runtime starting from the  XML configuration file created by the Configurator?</li>
  <li>Or in genereal how you would approach it?</li>
  </ul>
  
  <p>Best regards,
  Patric</p>