title: Deserializing Json into objects
body: <p>So the app I'm currently working with is going to be doing a lot of requests that all return json, would it be appropriate to create a class that holds the properties for each specific request thats going to return the json that can be converted into the properties of that class?</p>
  
  <p>For example, say I have 2 requests, one that returns a firstname, a surname and a job role, and I have another request that returns a business name, business location and business postcode, would it be OK to do:</p>
  
  <pre><code>class BusinessRetrieval {
    public string BusinessLocation{ get; set; }
    public string BusinessPostCode { get; set; }
  }
  
  class EmployeeRetrieval {
    public string Firstname { get; set; }
    public string Surname { get; set;}
    public string Postcode { get; set; }
  }
  </code></pre>
  
  <p>So now I have 2 classes that outline the properties that are going to be sent back once the request is made, now is it OK to just do:</p>
  
  <pre><code>BusinessRetrieval business = (BusinessRetrieval)JsonConvert.DeserializeObject(businessResponse, typeof(BusinessRetrieval));
  EmployeeRetrieval employee = (EmployeeRetrieval)JsonConvert.DeserializeObject(employeeResponse, typeof(EmployeeRetrieval));
  </code></pre>
  
  <p>What I'm asking here is this an OK to go around doing this? I'm going to be dealing with a lot of requests (10-15) and I plan on making a class for each that outline the properties that each response will give back, I feel as if this would be a nice way to structure it.</p>
  
  <p>Is this OK?</p>