I didn't remember that we were currently targeting framework v3.5. Will this matter? We might have some issues using this with some of the older code that we use it with, but I suppose that's not really a reason to upgrade and add async/await capability. Our older stuff couldn't use async anyway, so it could just stay on an older version of the library I think. Any other potential issues with jumping to 4.5.1?