Fix bug: exception filters appear on the wrong line

[MarcoRossignoli]

fixes #278

/cc @tonerdo @petli

[codecov]

Codecov Report

Merging #344 into master will decrease coverage by 0.16%.
The diff coverage is 76.59%.

@@            Coverage Diff             @@
##           master     #344      +/-   ##
==========================================
- Coverage    87.1%   86.94%   -0.17%     
==========================================
  Files          31       31              
  Lines        3033     3080      +47     
==========================================
+ Hits         2642     2678      +36     
- Misses        391      402      +11

[codecov]

Codecov Report

Merging #344 into master will decrease coverage by 0.16%.
The diff coverage is 76.59%.

@@            Coverage Diff             @@
##           master     #344      +/-   ##
==========================================
- Coverage    87.1%   86.94%   -0.17%     
==========================================
  Files          31       31              
  Lines        3033     3080      +47     
==========================================
+ Hits         2642     2678      +36     
- Misses        391      402      +11

[MarcoRossignoli]

@hughbe if you've some time can you try this update with your project?I cannot compile, build fail. Steps:

1. Clone this branch
2. build package

C:\git\coverlet (exceptionfilter -> origin)
λ msbuild /t:CreateNuGetPackage /p:Configuration=Release build.proj
...
Successfully created package 'C:\git\coverlet\build\Release\coverlet.console.1.4.1.nupkg'

3. Add Nuget.Config on root of you solution:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="localcoverlet" value="C:\git\coverlet\build\Release" />
    <add key="nuget" value="https://api.nuget.org/v3/index.json" />
  </packageSources>
</configuration>

You should refer coverlet.msbuild.2.5.1.nupkg and try to restore/test

/cc @pape77

[tonerdo]

LGTM! Ready to go once you fix up the merge conflicts

[MarcoRossignoli]

LGTM! Ready to go once you fix up the merge conflicts

It's not a merge issue, it's new github features "draft pr" https://github.blog/2019-02-14-introducing-draft-pull-requests/

I'm waiting if @hughbe can try this update, @pape77 says that it's ok, but two green light should be better

[MarcoRossignoli]

Use single :)

Done thank's!

[tonerdo]

It's not a merge issue, it's new github features "draft pr"

Lol, I didn't even read the message but just assumed it was a conflict.

[MarcoRossignoli]

@tonerdo no response I think we can go on with this

[MarcoRossignoli]

great thank's to @pape77 my private beta tester 😘