Fixed exception handling in TransmitAsync

[milopezc]

Fixed exception handling in TransmitAsync.

[codecov-io]

Codecov Report

Merging #321 into v2.1 will increase coverage by 0.21%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##             v2.1     #321      +/-   ##
==========================================
+ Coverage   89.42%   89.64%   +0.21%     
==========================================
  Files          31       31              
  Lines        1939     1951      +12     
  Branches      366      369       +3     
==========================================
+ Hits         1734     1749      +15     
+ Misses        157      156       -1     
+ Partials       48       46       -2

Impacted Files	Coverage Δ
src/StreamJsonRpc/Resources.Designer.cs	68.96% <100%> (+0.54%)	⬆️
src/StreamJsonRpc/JsonMessageFormatter.cs	86.63% <100%> (+0.06%)	⬆️
src/StreamJsonRpc/JsonRpc.cs	93.35% <100%> (+0.23%)	⬆️
src/StreamJsonRpc/ProxyGeneration.cs	98.28% <0%> (+0.34%)	⬆️
src/StreamJsonRpc/MessageHandlerBase.cs	97.61% <0%> (+2.38%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cfd93ae...73f0c5d. Read the comment docs.

[AArnott]

@milopezc, When I asked for you to rebase your changes to the v2.1 branch, it didn't require that you close your PR and open a new one. You can edit the target branch on an existing PR.
But more importantly, merely changing the target branch or opening a new PR with a different target branch is insufficient. You must rebase your commits to the v2.1 branch, which you evidently didn't do. Check the commits list in this PR and you'll see some commits unrelated to your change because they're still based on master.

You can fix this, without closing this PR, by following these steps on your machine:

git rebase --onto upstream/v2.1 8520f68~1 dev/milopezc/FixedTransmitExceptionHandling_959430 
git push -f

The commit ID that appears in that command line is your first commit related to this change. You're telling git to move your topic branch (last argument) to v2.1 (first argument), moving all commits up to and excluding the commit named. By stating your commit ID with ~1 at the end, that's git notation to identity the commit before it, so you're stating to consider the base of your topic branch to be just before your first commit, so that it moves your first commit.

That will take care of the rebasing. The next thing I would recommend is that you squash your commits since there are quite a few little fix-up commits. You can do that with these commands:

git merge upstream/v2.1
git reset --soft upstream/v2.1
git commit -m "Fixed exception handling in TransmitAsync"
git push -f

[AArnott]

Approved, once you get the build to pass.