Sep 24, 2015 08:58 AM|airic82|LINK
Maybe I'm making this all too complicated - I've been known to do that in the past. My thought was to try and abstract out the methods for making an API call as well as deserializing the data. That may be where I'm wrong.
I could still abstract out the MakeRequest method to get the XML response, but then each response type class can have it's own deserialize method.
That just seemed to create unnecessary redundancy, in my opinion. Plus, if I needed to change the way things were being deserialized, I'd have to change the method in every single class.
I hope my explanation makes sense. My ultimate goal is to have the most robust and clean code I can, so I appreciate your wisdom and advice here.